mirror of
https://github.com/samba-team/samba.git
synced 2025-01-14 19:24:43 +03:00
215 lines
15 KiB
HTML
215 lines
15 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter 5. Common errors"><link rel="next" href="FAQ-Printing.html" title="Chapter 7. Printing problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-features"></a>Chapter 6. Features</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2874269">How can I prevent my samba server from being used to distribute the Nimda worm?</a></dt><dt><a href="FAQ-features.html#id2874209">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874628">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874681">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874774">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874858">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2874883">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2874531">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2874581">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2874612">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874269"></a>How can I prevent my samba server from being used to distribute the Nimda worm?</h2></div></div><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>
|
||
</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><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,
|
||
</p><pre class="programlisting">
|
||
veto files = /*.{*}/
|
||
</pre><p>
|
||
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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874209"></a>How can I use samba as a fax server?</h2></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements:
|
||
</p><table class="simplelist" border="0" summary="Simple list"><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></table><p>
|
||
</p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax
|
||
manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874628"></a>Tools for printing faxes</h3></div></div><p>Your incomed faxes are in:
|
||
<tt>/var/spool/fax/incoming</tt>. Print it with:</p><pre class="programlisting">
|
||
for i in *
|
||
do
|
||
g3cat $i | g3tolj | lpr -P hp
|
||
done
|
||
</pre><p>
|
||
</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>g3cat $i | g3topbm - | ppmtopcx - >$i.pcx</b>
|
||
and view it with your favourite Windows tool (maybe paintbrush)
|
||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874681"></a>Making the fax-server</h3></div></div><p>fetch the file <tt>mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt>/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><pre class="programlisting">
|
||
if [ "$user" = "root" -o "$user" = "fax" -o \
|
||
"$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
|
||
</pre><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>/usr/local/etc/mgetty+sendfax/faxheader</tt></p><p>
|
||
Edit your /etc/printcap file:
|
||
</p><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>Now, edit your <tt>smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874774"></a>Installing the client drivers</h3></div></div><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:
|
||
</p><pre class="programlisting">
|
||
Fax-Nr: 123456789
|
||
</pre><p>
|
||
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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874858"></a>Example smb.conf</h3></div></div><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></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874883"></a>Samba doesn't work well together with DHCP!</h2></div></div><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>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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874531"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874581"></a>How do I convert between unix and dos text formats?</h2></div></div><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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874612"></a>Does samba have wins replication support?</h2></div></div><p>
|
||
At the time of writing there is currently being worked on a wins replication implementation(wrepld).
|
||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Common errors </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Printing problems</td></tr></table></div></body></html>
|