1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"><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�4.�Common errors"></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�5.�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">�</td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-features"></a>Chapter�5.�Features</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2818380">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2818433">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2818486">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2878038">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2820575">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2820600">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2878081">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2878131">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2878162">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818380"></a>How can I use samba as a fax server?</h2></div></div><div></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements: 2</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> 3</p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax 4manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2818433"></a>Tools for printing faxes</h3></div></div><div></div></div><p>Your incomed faxes are in: 5<tt class="filename">/var/spool/fax/incoming</tt>. Print it with:</p><pre class="programlisting"> 6for i in * 7do 8g3cat $i | g3tolj | lpr -P hp 9done 10</pre><p> 11</p><p> 12g3cat is in the tools-section, g3tolj is in the contrib-section 13for printing to HP lasers. 14</p><p> 15If you want to produce files for displaying and printing with Windows, use 16some tools from the pbm-package like the following command: <b class="command">g3cat $i | g3topbm - | ppmtopcx - >$i.pcx</b> 17and view it with your favourite Windows tool (maybe paintbrush) 18</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2818486"></a>Making the fax-server</h3></div></div><div></div></div><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 19edit fax/faxspool.in and reinstall or change the final 20/usr/local/bin/faxspool too. 21</p><pre class="programlisting"> 22if [ "$user" = "root" -o "$user" = "fax" -o \ 23 "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ] 24</pre><p>find the first line and change it to the second.</p><p> 25make sure you have pbmtext (from the pbm-package). This is 26needed for creating the small header line on each page. 27</p><p>Prepare your faxheader <tt class="filename">/usr/local/etc/mgetty+sendfax/faxheader</tt></p><p> 28Edit your /etc/printcap file: 29</p><pre class="programlisting"> 30# FAX 31lp3|fax:\ 32 :lp=/dev/null:\ 33 :sd=/usr/spool/lp3:\ 34 :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\ 35 :lf=/usr/spool/lp3/fax-log: 36</pre><p>Now, edit your <tt class="filename">smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878038"></a>Installing the client drivers</h3></div></div><div></div></div><p> 37Now you have a printer called "fax" which can be used via 38TCP/IP-printing (lpd-system) or via SAMBA (windows printing). 39</p><p> 40On every system you are able to produce postscript-files you 41are ready to fax. 42</p><p> 43On Windows 3.1 95 and NT: 44</p><p> 45Install a printer wich produces postscript output, 46 e.g. apple laserwriter 47</p><p>Connect the "fax" to your printer.</p><p> 48Now write your first fax. Use your favourite wordprocessor, 49write, winword, notepad or whatever you want, and start 50with the headerpage. 51</p><p> 52Usually each fax has a header page. It carries your name, 53your address, your phone/fax-number. 54</p><p> 55It carries also the recipient, his address and his *** fax 56number ***. Now here is the trick: 57</p><p> 58Use the text: 59</p><pre class="programlisting"> 60Fax-Nr: 123456789 61</pre><p> 62as the recipients fax-number. Make sure this text does not 63occur in regular text ! Make sure this text is not broken 64by formatting information, e.g. format it as a single entity. 65(Windows Write and Win95 Wordpad are functional, maybe newer 66 versions of Winword are breaking formatting information). 67</p><p> 68The trick is that postscript output is human readable and 69the faxfilter program scans the text for this pattern and 70uses the found number as the fax-destination-number. 71</p><p> 72Now print your fax through the fax-printer and it will be 73queued for later transmission. Use faxrunq for sending the 74queue out. 75</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2820575"></a>Example smb.conf</h3></div></div><div></div></div><pre class="programlisting"> 76[global] 77 printcap name = /etc/printcap 78 print command = /usr/bin/lpr -r -P %p %s 79 lpq command = /usr/bin/lpq -P %p 80 lprm command = /usr/bin/lprm -P %p %j 81 82[fax] 83 comment = FAX (mgetty+sendfax) 84 path = /tmp 85 printable = yes 86 public = yes 87 writable = no 88 create mode = 0700 89 browseable = yes 90 guest ok = no 91</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2820600"></a>Samba doesn't work well together with DHCP!</h2></div></div><div></div></div><p> 92We wish to help those folks who wish to use the ISC DHCP Server and provide 93sample configuration settings. Most operating systems today come ship with 94the ISC DHCP Server. ISC DHCP is available from: 95<a href="ftp://ftp.isc.org/isc/dhcp" target="_top">ftp://ftp.isc.org/isc/dhcp</a> 96</p><p> 97Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows 98NT/2000) will lead to problems with browsing and with general network 99operation. Windows 9X/ME users often report problems where the TCP/IP and related 100network settings will inadvertantly become reset at machine start-up resulting 101in loss of configuration settings. This results in increased maintenance 102overheads as well as serious user frustration. 103</p><p> 104In recent times users on one mailing list incorrectly attributed the cause of 105network operating problems to incorrect configuration of Samba. 106</p><p> 107One user insisted that the only way to provent Windows95 from periodically 108performing a full system reset and hardware detection process on start-up was 109to install the NetBEUI protocol in addition to TCP/IP. This assertion is not 110correct. 111</p><p> 112In the first place, there is NO need for NetBEUI. All Microsoft Windows clients 113natively run NetBIOS over TCP/IP, and that is the only protocol that is 114recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will 115cause problems with browse list operation on most networks. Even Windows NT 116networks experience these problems when incorrectly configured Windows95 117systems share the same name space. It is important that only those protocols 118that are strictly needed for site specific reasons should EVER be installed. 119</p><p> 120Secondly, and totally against common opinion, DHCP is NOT an evil design but is 121an extension of the BOOTP protocol that has been in use in Unix environments 122for many years without any of the melt-down problems that some sensationalists 123would have us believe can be experienced with DHCP. In fact, DHCP in covered by 124rfc1541 and is a very safe method of keeping an MS Windows desktop environment 125under control and for ensuring stable network operation. 126</p><p> 127Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95 128store all network configuration settings a registry. There are a few reports 129from MS Windows network administrators that warrant mention here. It would appear 130that when one sets certain MS TCP/IP protocol settings (either directly or via 131DHCP) that these do get written to the registry. Even though a subsequent 132change of setting may occur the old value may persist in the registry. This 133has been known to create serious networking problems. 134</p><p> 135An example of this occurs when a manual TCP/IP environment is configured to 136include a NetBIOS Scope. In this event, when the administrator then changes the 137configuration of the MS TCP/IP protocol stack, without first deleting the 138current settings, by simply checking the box to configure the MS TCP/IP stack 139via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be 140applied to the resulting DHCP offered settings UNLESS the DHCP server also sets 141a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS 142Scope from your DHCP server. The can be done in the dhcpd.conf file with the 143parameter: 144<b class="command">option netbios-scope "";</b> 145</p><p> 146While it is true that the Microsoft DHCP server that comes with Windows NT 147Server provides only a sub-set of rfc1533 functionality this is hardly an issue 148in those sites that already have a large investment and commitment to Unix 149systems and technologies. The current state of the art of the DHCP Server 150specification in covered in rfc2132. 151</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878081"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><div></div></div><p> 152SMB network clients need to be configured so that all standard TCP/IP name to 153address resolution works correctly. Once this has been achieved the SMB 154environment provides additional tools and services that act as helper agents in 155the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One 156such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it 157in their Windows NT Server implementation WINS (Windows Internet Name Server). 158</p><p> 159A client needs to be configured so that it has a unique Machine (Computer) 160Name. 161</p><p> 162This can be done, but needs a few NT registry hacks and you need to be able to 163speak UNICODE, which is of course no problem for a True Wizzard(tm) :) 164Instructions on how to do this (including a small util for less capable 165Wizzards) can be found at 166</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><div><h2 class="title" style="clear: both"><a name="id2878131"></a>How do I convert between unix and dos text formats?</h2></div></div><div></div></div><p> 167Jim barry has written an <a href="ftp://samba.org/pub/samba/contributed/fixcrlf.zip" target="_top"> 168excellent drag-and-drop cr/lf converter for 169windows</a>. Just drag your file onto the icon and it converts the file. 170</p><p> 171The utilities unix2dos and dos2unix(in the mtools package) should do 172the job under unix. 173</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878162"></a>Does samba have wins replication support?</h2></div></div><div></div></div><p> 174At the time of writing there is currently being worked on a wins replication implementation(wrepld). 175</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">�</td></tr><tr><td width="40%" align="left" valign="top">Chapter�4.�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">�</td></tr></table></div></body></html> 176