summaryrefslogtreecommitdiff
path: root/docs/faq
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq')
-rw-r--r--docs/faq/faq-clientapp.html (renamed from docs/faq/clientapp.html)54
-rw-r--r--docs/faq/faq-config.html163
-rw-r--r--docs/faq/faq-errors.html (renamed from docs/faq/errors.html)63
-rw-r--r--docs/faq/faq-features.html538
-rw-r--r--docs/faq/faq-general.html (renamed from docs/faq/general.html)34
-rw-r--r--docs/faq/faq-install.html (renamed from docs/faq/install.html)64
-rw-r--r--docs/faq/faq-printing.html181
7 files changed, 994 insertions, 103 deletions
diff --git a/docs/faq/clientapp.html b/docs/faq/faq-clientapp.html
index b48e236377..3a85fb4f5a 100644
--- a/docs/faq/clientapp.html
+++ b/docs/faq/faq-clientapp.html
@@ -5,16 +5,16 @@
>Specific client application problems</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="PREVIOUS"
TITLE="Configuration problems"
-HREF="config.html"><LINK
+HREF="faq-config.html"><LINK
REL="NEXT"
TITLE="Common errors"
-HREF="errors.html"></HEAD
+HREF="faq-errors.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="config.html"
+HREF="faq-config.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="errors.html"
+HREF="faq-errors.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="CLIENTAPP"
+NAME="FAQ-CLIENTAPP"
></A
>Chapter 4. Specific client application problems</H1
><DIV
@@ -77,9 +77,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN175"
-></A
->4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
+NAME="AEN178"
+>4.1. MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</A
+></H1
><P
>When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
@@ -98,9 +98,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN180"
-></A
->4.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
+NAME="AEN183"
+>4.2. How to use a Samba share as an administrative share for MS Office, etc.</A
+></H1
><P
>Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
@@ -133,16 +133,16 @@ set the following parameters on the share containing it:</P
><P
><PRE
CLASS="PROGRAMLISTING"
-> [MSOP95]
- path = /where_you_put_it
- comment = Your comment
- volume = "The_CD_ROM_Label"
- read only = yes
- available = yes
- share modes = no
- locking = no
- browseable = yes
- public = yes</PRE
+>[MSOP95]
+ path = /where_you_put_it
+ comment = Your comment
+ volume = "The_CD_ROM_Label"
+ read only = yes
+ available = yes
+ share modes = no
+ locking = no
+ browseable = yes
+ public = yes</PRE
></P
></LI
><LI
@@ -160,9 +160,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN195"
-></A
->4.3. Microsoft Access database opening errors</H1
+NAME="AEN198"
+>4.3. Microsoft Access database opening errors</A
+></H1
><P
>Here are some notes on running MS-Access on a Samba drive from <A
HREF="stefank@esi.com.au"
@@ -210,7 +210,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="config.html"
+HREF="faq-config.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -228,7 +228,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="errors.html"
+HREF="faq-errors.html"
ACCESSKEY="N"
>Next</A
></TD
diff --git a/docs/faq/faq-config.html b/docs/faq/faq-config.html
new file mode 100644
index 0000000000..67b5ca2b35
--- /dev/null
+++ b/docs/faq/faq-config.html
@@ -0,0 +1,163 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Configuration problems</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Compiling and installing Samba on a Unix host"
+HREF="faq-install.html"><LINK
+REL="NEXT"
+TITLE="Specific client application problems"
+HREF="faq-clientapp.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="faq-install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="faq-clientapp.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="FAQ-CONFIG"
+></A
+>Chapter 3. Configuration problems</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN169"
+>3.1. I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
+></H1
+><P
+>When you have a user in 'admin users', samba will always do file operations for
+this user as 'root', even if 'force user' has been set.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN172"
+>3.2. I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</A
+></H1
+><P
+>Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these
+passwords to the unix password database, so it needs it's own user database. You can
+add users to this database using "smbpasswd -a user-name".</P
+><P
+>See also the "User database" chapter of the samba HOWTO Collection.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="faq-install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="faq-clientapp.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Compiling and installing Samba on a Unix host</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Specific client application problems</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/errors.html b/docs/faq/faq-errors.html
index 08da5e5db0..20eca6adea 100644
--- a/docs/faq/errors.html
+++ b/docs/faq/faq-errors.html
@@ -5,16 +5,16 @@
>Common errors</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="PREVIOUS"
TITLE="Specific client application problems"
-HREF="clientapp.html"><LINK
+HREF="faq-clientapp.html"><LINK
REL="NEXT"
TITLE="Features"
-HREF="features.html"></HEAD
+HREF="faq-features.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="clientapp.html"
+HREF="faq-clientapp.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="features.html"
+HREF="faq-features.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="ERRORS"
+NAME="FAQ-ERRORS"
></A
>Chapter 5. Common errors</H1
><DIV
@@ -77,9 +77,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN206"
-></A
->5.1. Not listening for calling name</H1
+NAME="AEN209"
+>5.1. Not listening for calling name</A
+></H1
><P
><PRE
CLASS="PROGRAMLISTING"
@@ -103,9 +103,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN213"
-></A
->5.2. System Error 1240</H1
+NAME="AEN216"
+>5.2. System Error 1240</A
+></H1
><P
>System error 1240 means that the client is refusing to talk
to a non-encrypting server. Microsoft changed WinNT in service
@@ -139,9 +139,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN220"
-></A
->5.3. smbclient ignores -N !</H1
+NAME="AEN223"
+>5.3. smbclient ignores -N !</A
+></H1
><P
><SPAN
CLASS="QUOTE"
@@ -174,9 +174,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN229"
-></A
->5.4. The data on the CD-Drive I've shared seems to be corrupted!</H1
+NAME="AEN232"
+>5.4. The data on the CD-Drive I've shared seems to be corrupted!</A
+></H1
><P
>Some OSes (notably Linux) default to auto detection of file type on
cdroms and do cr/lf translation. This is a very bad idea when use with
@@ -190,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN233"
-></A
->5.5. Why can users access home directories of other users?</H1
+NAME="AEN236"
+>5.5. Why can users access home directories of other users?</A
+></H1
><P
><SPAN
CLASS="QUOTE"
@@ -248,12 +248,23 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN246"
-></A
->5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</H1
+NAME="AEN249"
+>5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
+></H1
><P
>A domain controller has to announce on the network who it is. This usually takes a while.</P
></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN252"
+>5.7. I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</A
+></H1
+><P
+>Your loopback device isn't working correctly. Make sure it's running.</P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -271,7 +282,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="clientapp.html"
+HREF="faq-clientapp.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -289,7 +300,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="features.html"
+HREF="faq-features.html"
ACCESSKEY="N"
>Next</A
></TD
diff --git a/docs/faq/faq-features.html b/docs/faq/faq-features.html
new file mode 100644
index 0000000000..392820c21f
--- /dev/null
+++ b/docs/faq/faq-features.html
@@ -0,0 +1,538 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Features</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Common errors"
+HREF="faq-errors.html"><LINK
+REL="NEXT"
+TITLE="Printing problems"
+HREF="faq-printing.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="faq-errors.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="faq-printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="FAQ-FEATURES"
+></A
+>Chapter 6. Features</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN257"
+>6.1. How can I prevent my samba server from being used to distribute the Nimda worm?</A
+></H1
+><P
+>Author: HASEGAWA Yosuke (translated by <A
+HREF="monyo@samba.gr.jp"
+TARGET="_top"
+>TAKAHASHI Motonobu</A
+>)</P
+><P
+>Nimba Worm is infected through shared disks on a network, as well as through
+Microsoft IIS, Internet Explorer and mailer of Outlook series.</P
+><P
+>At this time, the worm copies itself by the name *.nws and *.eml on
+the shared disk, moreover, by the name of Riched20.dll in the folder
+where *.doc file is included.</P
+><P
+>To prevent infection through the shared disk offered by Samba, set
+up as follows:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ ...
+ # This can break Administration installations of Office2k.
+ # in that case, don't veto the riched20.dll
+ veto files = /*.eml/*.nws/riched20.dll/</PRE
+></P
+><P
+>By setting the "veto files" parameter, matched files on the Samba
+server are completely hidden from the clients and making it impossible
+to access them at all.</P
+><P
+>In addition to it, the following setting is also pointed out by the
+samba-jp:09448 thread: when the
+"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on
+a Samba server, it is visible only as "readme.txt" and dangerous
+code may be executed if this file is double-clicked.</P
+><P
+>Setting the following,
+<PRE
+CLASS="PROGRAMLISTING"
+> veto files = /*.{*}/</PRE
+>
+any files having CLSID in its file extension will be inaccessible from any
+clients.</P
+><P
+>This technical article is created based on the discussion of
+samba-jp:09448 and samba-jp:10900 threads.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN271"
+>6.2. How can I use samba as a fax server?</A
+></H1
+><P
+>Contributor: <A
+HREF="mailto:zuber@berlin.snafu.de"
+TARGET="_top"
+>Gerhard Zuber</A
+></P
+><P
+>Requirements:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>UNIX box (Linux preferred) with SAMBA and a faxmodem</TD
+></TR
+><TR
+><TD
+>ghostscript package</TD
+></TR
+><TR
+><TD
+>mgetty+sendfax package</TD
+></TR
+><TR
+><TD
+>pbm package (portable bitmap tools)</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>First, install and configure the required packages. Be sure to read the mgetty+sendfax
+manual carefully.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN282"
+>6.2.1. Tools for printing faxes</A
+></H2
+><P
+>Your incomed faxes are in:
+<TT
+CLASS="FILENAME"
+>/var/spool/fax/incoming</TT
+>. Print it with:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>for i in *
+do
+g3cat $i | g3tolj | lpr -P hp
+done</PRE
+></P
+><P
+>g3cat is in the tools-section, g3tolj is in the contrib-section
+for printing to HP lasers.</P
+><P
+>If you want to produce files for displaying and printing with Windows, use
+some tools from the pbm-package like the following command: <B
+CLASS="COMMAND"
+>g3cat $i | g3topbm - | ppmtopcx - &#62;$i.pcx</B
+>
+and view it with your favourite Windows tool (maybe paintbrush)</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN291"
+>6.2.2. Making the fax-server</A
+></H2
+><P
+>fetch the file <TT
+CLASS="FILENAME"
+>mgetty+sendfax/frontends/winword/faxfilter</TT
+> and place it in <TT
+CLASS="FILENAME"
+>/usr/local/etc/mgetty+sendfax/</TT
+>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</P
+><P
+>prepare your faxspool file as mentioned in this file
+edit fax/faxspool.in and reinstall or change the final
+/usr/local/bin/faxspool too.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>if [ "$user" = "root" -o "$user" = "fax" -o \
+ "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]</PRE
+></P
+><P
+>find the first line and change it to the second.</P
+><P
+>make sure you have pbmtext (from the pbm-package). This is
+needed for creating the small header line on each page.</P
+><P
+>Prepare your faxheader <TT
+CLASS="FILENAME"
+>/usr/local/etc/mgetty+sendfax/faxheader</TT
+></P
+><P
+>Edit your /etc/printcap file:
+<PRE
+CLASS="PROGRAMLISTING"
+># FAX
+lp3|fax:\
+ :lp=/dev/null:\
+ :sd=/usr/spool/lp3:\
+ :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
+ :lf=/usr/spool/lp3/fax-log:</PRE
+></P
+><P
+>Now, edit your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> so you have a smb based printer named "fax"</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN307"
+>6.2.3. Installing the client drivers</A
+></H2
+><P
+>Now you have a printer called "fax" which can be used via
+TCP/IP-printing (lpd-system) or via SAMBA (windows printing).</P
+><P
+>On every system you are able to produce postscript-files you
+are ready to fax.</P
+><P
+>On Windows 3.1 95 and NT:</P
+><P
+>Install a printer wich produces postscript output,
+ e.g. apple laserwriter</P
+><P
+>Connect the "fax" to your printer.</P
+><P
+>Now write your first fax. Use your favourite wordprocessor,
+write, winword, notepad or whatever you want, and start
+with the headerpage.</P
+><P
+>Usually each fax has a header page. It carries your name,
+your address, your phone/fax-number.</P
+><P
+>It carries also the recipient, his address and his *** fax
+number ***. Now here is the trick:</P
+><P
+>Use the text:
+<PRE
+CLASS="PROGRAMLISTING"
+>Fax-Nr: 123456789</PRE
+>
+as the recipients fax-number. Make sure this text does not
+occur in regular text ! Make sure this text is not broken
+by formatting information, e.g. format it as a single entity.
+(Windows Write and Win95 Wordpad are functional, maybe newer
+ versions of Winword are breaking formatting information).</P
+><P
+>The trick is that postscript output is human readable and
+the faxfilter program scans the text for this pattern and
+uses the found number as the fax-destination-number.</P
+><P
+>Now print your fax through the fax-printer and it will be
+queued for later transmission. Use faxrunq for sending the
+queue out.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN321"
+>6.2.4. Example smb.conf</A
+></H2
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ printcap name = /etc/printcap
+ print command = /usr/bin/lpr -r -P %p %s
+ lpq command = /usr/bin/lpq -P %p
+ lprm command = /usr/bin/lprm -P %p %j
+
+[fax]
+ comment = FAX (mgetty+sendfax)
+ path = /tmp
+ printable = yes
+ public = yes
+ writable = no
+ create mode = 0700
+ browseable = yes
+ guest ok = no</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN325"
+>6.3. Samba doesn't work well together with DHCP!</A
+></H1
+><P
+>We wish to help those folks who wish to use the ISC DHCP Server and provide
+sample configuration settings. Most operating systems today come ship with
+the ISC DHCP Server. ISC DHCP is available from:
+<A
+HREF="ftp://ftp.isc.org/isc/dhcp"
+TARGET="_top"
+>ftp://ftp.isc.org/isc/dhcp</A
+></P
+><P
+>Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows
+NT/2000) will lead to problems with browsing and with general network
+operation. Windows 9X/ME users often report problems where the TCP/IP and related
+network settings will inadvertantly become reset at machine start-up resulting
+in loss of configuration settings. This results in increased maintenance
+overheads as well as serious user frustration.</P
+><P
+>In recent times users on one mailing list incorrectly attributed the cause of
+network operating problems to incorrect configuration of Samba.</P
+><P
+>One user insisted that the only way to provent Windows95 from periodically
+performing a full system reset and hardware detection process on start-up was
+to install the NetBEUI protocol in addition to TCP/IP. This assertion is not
+correct.</P
+><P
+>In the first place, there is NO need for NetBEUI. All Microsoft Windows clients
+natively run NetBIOS over TCP/IP, and that is the only protocol that is
+recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will
+cause problems with browse list operation on most networks. Even Windows NT
+networks experience these problems when incorrectly configured Windows95
+systems share the same name space. It is important that only those protocols
+that are strictly needed for site specific reasons should EVER be installed.</P
+><P
+>Secondly, and totally against common opinion, DHCP is NOT an evil design but is
+an extension of the BOOTP protocol that has been in use in Unix environments
+for many years without any of the melt-down problems that some sensationalists
+would have us believe can be experienced with DHCP. In fact, DHCP in covered by
+rfc1541 and is a very safe method of keeping an MS Windows desktop environment
+under control and for ensuring stable network operation.</P
+><P
+>Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95
+store all network configuration settings a registry. There are a few reports
+from MS Windows network administrators that warrant mention here. It would appear
+that when one sets certain MS TCP/IP protocol settings (either directly or via
+DHCP) that these do get written to the registry. Even though a subsequent
+change of setting may occur the old value may persist in the registry. This
+has been known to create serious networking problems.</P
+><P
+>An example of this occurs when a manual TCP/IP environment is configured to
+include a NetBIOS Scope. In this event, when the administrator then changes the
+configuration of the MS TCP/IP protocol stack, without first deleting the
+current settings, by simply checking the box to configure the MS TCP/IP stack
+via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be
+applied to the resulting DHCP offered settings UNLESS the DHCP server also sets
+a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS
+Scope from your DHCP server. The can be done in the dhcpd.conf file with the
+parameter:
+<B
+CLASS="COMMAND"
+>option netbios-scope "";</B
+></P
+><P
+>While it is true that the Microsoft DHCP server that comes with Windows NT
+Server provides only a sub-set of rfc1533 functionality this is hardly an issue
+in those sites that already have a large investment and commitment to Unix
+systems and technologies. The current state of the art of the DHCP Server
+specification in covered in rfc2132.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN338"
+>6.4. How can I assign NetBIOS names to clients with DHCP?</A
+></H1
+><P
+>SMB network clients need to be configured so that all standard TCP/IP name to
+address resolution works correctly. Once this has been achieved the SMB
+environment provides additional tools and services that act as helper agents in
+the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One
+such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it
+in their Windows NT Server implementation WINS (Windows Internet Name Server).</P
+><P
+>A client needs to be configured so that it has a unique Machine (Computer)
+Name.</P
+><P
+>This can be done, but needs a few NT registry hacks and you need to be able to
+speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
+Instructions on how to do this (including a small util for less capable
+Wizzards) can be found at</P
+><P
+><A
+HREF="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html"
+TARGET="_top"
+>http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN345"
+>6.5. How do I convert between unix and dos text formats?</A
+></H1
+><P
+>Jim barry has written an <A
+HREF="ftp://samba.org/pub/samba/contributed/fixcrlf.zip"
+TARGET="_top"
+>excellent drag-and-drop cr/lf converter for
+windows</A
+>. Just drag your file onto the icon and it converts the file.</P
+><P
+>The utilities unix2dos and dos2unix(in the mtools package) should do
+the job under unix.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN350"
+>6.6. Does samba have wins replication support?</A
+></H1
+><P
+>At the time of writing there is currently being worked on a wins replication implementation(wrepld).</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="faq-errors.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="faq-printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Common errors</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Printing problems</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/general.html b/docs/faq/faq-general.html
index 5a42678cb6..15dce949c9 100644
--- a/docs/faq/general.html
+++ b/docs/faq/faq-general.html
@@ -5,7 +5,7 @@
>General Information</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
@@ -14,7 +14,7 @@ TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="NEXT"
TITLE="Compiling and installing Samba on a Unix host"
-HREF="install.html"></HEAD
+HREF="faq-install.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="install.html"
+HREF="faq-install.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="GENERAL"
+NAME="FAQ-GENERAL"
></A
>Chapter 1. General Information</H1
><DIV
@@ -78,8 +78,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN12"
-></A
->1.1. Where can I get it?</H1
+>1.1. Where can I get it?</A
+></H1
><P
>The Samba suite is available at the <A
HREF="http://samba.org/"
@@ -93,8 +93,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN16"
-></A
->1.2. What do the version numbers mean?</H1
+>1.2. What do the version numbers mean?</A
+></H1
><P
>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
@@ -141,7 +141,7 @@ levels are released which give us the pXX series, for example 1.9.16p2.</TD
></TABLE
><P
></P
->&#13;</P
+></P
><P
>So the progression goes:
@@ -167,8 +167,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN28"
-></A
->1.3. What platforms are supported?</H1
+>1.3. What platforms are supported?</A
+></H1
><P
>Many different platforms have run Samba successfully. The platforms
most widely used and thus best tested are Linux and SunOS.</P
@@ -343,8 +343,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN71"
-></A
->1.4. How do I subscribe to the Samba Mailing Lists?</H1
+>1.4. How do I subscribe to the Samba Mailing Lists?</A
+></H1
><P
>Look at <A
HREF="http://samba.org/samba/archives.html"
@@ -358,14 +358,14 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN75"
-></A
->1.5. Pizza supply details</H1
+>1.5. Pizza supply details</A
+></H1
><P
>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
pizza. This calls for a little organisation when the pizza donor is
-twenty thousand kilometres away, but it has been done.&#13;</P
+twenty thousand kilometres away, but it has been done.</P
><P
>Method 1: Ring up your local branch of an international pizza chain
and see if they honour their vouchers internationally. Pizza Hut do,
@@ -421,7 +421,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="install.html"
+HREF="faq-install.html"
ACCESSKEY="N"
>Next</A
></TD
diff --git a/docs/faq/install.html b/docs/faq/faq-install.html
index 23403ab96b..646b65bf7f 100644
--- a/docs/faq/install.html
+++ b/docs/faq/faq-install.html
@@ -5,16 +5,16 @@
>Compiling and installing Samba on a Unix host</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="PREVIOUS"
TITLE="General Information"
-HREF="general.html"><LINK
+HREF="faq-general.html"><LINK
REL="NEXT"
TITLE="Configuration problems"
-HREF="config.html"></HEAD
+HREF="faq-config.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="general.html"
+HREF="faq-general.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="config.html"
+HREF="faq-config.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="INSTALL"
+NAME="FAQ-INSTALL"
></A
>Chapter 2. Compiling and installing Samba on a Unix host</H1
><DIV
@@ -78,8 +78,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN84"
-></A
->2.1. I can't see the Samba server in any browse lists!</H1
+>2.1. I can't see the Samba server in any browse lists!</A
+></H1
><P
>See Browsing.html in the docs directory of the samba source
for more information on browsing.</P
@@ -101,8 +101,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN89"
-></A
->2.2. Some files that I KNOW are on the server doesn't show up when I view the files from my client!</H1
+>2.2. Some files that I KNOW are on the server don't show up when I view the files from my client!</A
+></H1
><P
>See the next question.</P
></DIV
@@ -112,8 +112,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN92"
-></A
->2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</H1
+>2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</A
+></H1
><P
>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
@@ -132,8 +132,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN96"
-></A
->2.4. My client reports "cannot locate specified computer" or similar</H1
+>2.4. My client reports "cannot locate specified computer" or similar</A
+></H1
><P
>This indicates one of three things: You supplied an incorrect server
name, the underlying TCP/IP layer is not working correctly, or the
@@ -167,8 +167,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN103"
-></A
->2.5. My client reports "cannot locate specified share name" or similar</H1
+>2.5. My client reports "cannot locate specified share name" or similar</A
+></H1
><P
>This message indicates that your client CAN locate the specified
server, which is a good start, but that it cannot find a service of
@@ -210,8 +210,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN112"
-></A
->2.6. Printing doesn't work</H1
+>2.6. Printing doesn't work</A
+></H1
><P
>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.,
@@ -246,8 +246,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN120"
-></A
->2.7. My client reports "This server is not configured to list shared resources"</H1
+>2.7. My client reports "This server is not configured to list shared resources"</A
+></H1
><P
>Your guest account is probably invalid for some reason. Samba uses the
guest account for browsing in smbd. Check that your guest account is
@@ -261,8 +261,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN124"
-></A
->2.8. Log message "you appear to have a trapdoor uid system"</H1
+>2.8. Log message "you appear to have a trapdoor uid system"</A
+></H1
><P
>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
@@ -302,8 +302,8 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN132"
-></A
->2.9. Why are my file's timestamps off by an hour, or by a few hours?</H1
+>2.9. Why are my file's timestamps off by an hour, or by a few hours?</A
+></H1
><P
>This is from Paul Eggert eggert@twinsun.com.</P
><P
@@ -419,19 +419,17 @@ CLASS="SECT1"
CLASS="SECT1"
><A
NAME="AEN155"
-></A
->2.10. How do I set the printer driver name correctly?</H1
-><P
->Question:</P
+>2.10. How do I set the printer driver name correctly?</A
+></H1
><P
-><SPAN
+>Question:
+<SPAN
CLASS="QUOTE"
>" On NT, I opened "Printer Manager" and "Connect to Printer".
Enter ["\\ptdi270\ps1"] in the box of printer. I got the
following error message
"</SPAN
->
- </P
+></P
><P
> <PRE
CLASS="PROGRAMLISTING"
@@ -478,7 +476,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="general.html"
+HREF="faq-general.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -496,7 +494,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="config.html"
+HREF="faq-config.html"
ACCESSKEY="N"
>Next</A
></TD
diff --git a/docs/faq/faq-printing.html b/docs/faq/faq-printing.html
new file mode 100644
index 0000000000..cfe93d8ee8
--- /dev/null
+++ b/docs/faq/faq-printing.html
@@ -0,0 +1,181 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Printing problems</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Features"
+HREF="faq-features.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="faq-features.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+>&nbsp;</TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="FAQ-PRINTING"
+></A
+>Chapter 7. Printing problems</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN359"
+>7.1. setdriver or cupsaddsmb failes</A
+></H1
+><P
+>setdriver expects the following setup:
+
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.</TD
+></TR
+><TR
+><TD
+>printer admins has to be defined in [global]</TD
+></TR
+><TR
+><TD
+>upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.</TD
+></TR
+><TR
+><TD
+>Make sure that the user you're connecting as is able to write to the print$ directories</TD
+></TR
+><TR
+><TD
+>Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)</TD
+></TR
+><TR
+><TD
+>Use setdriver to associate the driver with a printer</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>&#13;</P
+><P
+>The setdriver call will fail if the printer doesn't already exist in
+samba's view of the world. Either create the printer in cups and
+restart samba, or create an add printer command (see smb.conf doco)
+and use RPC calls to create a printer. NB the add printer command MUST
+return a single line of text indicating which port the printer was
+added on. If it doesn't, Samba won't reload the printer
+definitions. Although samba doesn't really support the notion of
+ports, suitable add printer command and enumport command settings can
+allow you pretty good remote control of the samba printer setup.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="faq-features.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Features</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
generated by cgit (git 2.34.1) at 2024-11-01 21:00:53 +0000