1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�39.�Analyzing and Solving Samba Problems</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part�V.�Troubleshooting"><link rel="prev" href="diagnosis.html" title="Chapter�38.�The Samba Checklist"><link rel="next" href="bugreport.html" title="Chapter�40.�Reporting Bugs"></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�39.�Analyzing and Solving Samba Problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a>�</td><th width="60%" align="center">Part�V.�Troubleshooting</th><td width="20%" align="right">�<a accesskey="n" href="bugreport.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter�39.�Analyzing and Solving Samba Problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="orgname">Samba Team</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="problems.html#id2684689">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id2684741">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id2684997">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685047">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id2685190">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id2685523">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685560">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id2685735">How to Get Off the Mailing Lists</a></span></dt></dl></div><p> 2<a class="indexterm" name="id2684663"></a> 3<a class="indexterm" name="id2684670"></a> 4<a class="indexterm" name="id2684676"></a> 5There are many sources of information available in the form of mailing lists, RFCs, and documentation. The 6documentation that comes with the Samba distribution contains good explanations of general SMB topics such as 7browsing. 8</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2684689"></a>Diagnostics Tools</h2></div></div></div><p> 9<a class="indexterm" name="id2684696"></a> 10<a class="indexterm" name="id2684703"></a> 11<a class="indexterm" name="id2684710"></a> 12<a class="indexterm" name="id2684717"></a> 13<a class="indexterm" name="id2684724"></a> 14With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself 15provides rather useful information, but in some cases you might have to fall back to using a 16<span class="emphasis"><em>sniffer</em></span>. A sniffer is a program that listens on your LAN, analyzes the data sent on it, 17and displays it on the screen. 18</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2684741"></a>Debugging with Samba Itself</h3></div></div></div><p> 19<a class="indexterm" name="id2684749"></a> 20<a class="indexterm" name="id2684756"></a> 21<a class="indexterm" name="id2684762"></a> 22<a class="indexterm" name="id2684769"></a> 23<a class="indexterm" name="id2684776"></a> 24<a class="indexterm" name="id2684783"></a> 25<a class="indexterm" name="id2684790"></a> 26One of the best diagnostic tools for debugging problems is Samba itself. You can use the <code class="option">-d 27option</code> for both <span class="application">smbd</span> and <span class="application">nmbd</span> to specify the <a class="link" href="smb.conf.5.html#DEBUGLEVEL" target="_top">debug level</a> at which to run. 28See the man pages for <code class="literal">smbd, nmbd</code>, and <code class="filename">smb.conf</code> for more information regarding debugging 29options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords). 30</p><p> 31<a class="indexterm" name="id2684844"></a> 32<a class="indexterm" name="id2684851"></a> 33<a class="indexterm" name="id2684858"></a> 34<a class="indexterm" name="id2684865"></a> 35<a class="indexterm" name="id2684872"></a> 36<a class="indexterm" name="id2684878"></a> 37<a class="indexterm" name="id2684885"></a> 38Another helpful method of debugging is to compile Samba using the <code class="literal">gcc -g </code> flag. This will 39include debug information in the binaries and allow you to attach <code class="literal">gdb</code> to the running 40<code class="literal">smbd/nmbd</code> process. To attach <code class="literal">gdb</code> to an <code class="literal">smbd</code> process 41for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going 42down to the domain box is sufficient (at least, the first time you join the domain) to generate a 43<em class="parameter"><code>LsaEnumTrustedDomains</code></em>. Thereafter, the workstation maintains an open connection and 44there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout). So, in 45between pressing <code class="literal">ctrl-alt-delete</code> and actually typing in your password, you can attach 46<code class="literal">gdb</code> and continue. 47</p><p> 48Some useful Samba commands worth investigating are: 49<a class="indexterm" name="id2684954"></a> 50<a class="indexterm" name="id2684961"></a> 51</p><pre class="screen"> 52<code class="prompt">$ </code><strong class="userinput"><code>testparm | more</code></strong> 53<code class="prompt">$ </code><strong class="userinput"><code>smbclient -L //{netbios name of server}</code></strong> 54</pre><p> 55</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2684997"></a>Tcpdump</h3></div></div></div><p> 56<a class="indexterm" name="id2685004"></a> 57<a class="indexterm" name="id2685011"></a> 58<a class="indexterm" name="id2685018"></a> 59<a class="ulink" href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first 60UNIX sniffer with SMB support. It is a command-line utility and 61now, its SMB support is somewhat lagging that of <code class="literal">ethereal</code> 62and <code class="literal">tethereal</code>. 63</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685047"></a>Ethereal</h3></div></div></div><p> 64<a class="indexterm" name="id2685055"></a> 65<a class="ulink" href="http://www.ethereal.com/" target="_top">Ethereal</a> is a graphical sniffer, available for both UNIX (Gtk) 66and Windows. Ethereal's SMB support is quite good. For details on the use of <code class="literal">ethereal</code>, read 67the well-written Ethereal User Guide. 68</p><div class="figure"><a name="ethereal1"></a><p class="title"><b>Figure�39.1.�Starting a Capture.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ethereal1.png" alt="Starting a Capture."></div></div></div><br class="figure-break"><p> 69<a class="indexterm" name="id2685118"></a> 70Listen for data on ports 137, 138, 139, and 445. For example, use the filter <strong class="userinput"><code>port 137, port 138, 71port 139, or port 445</code></strong> as seen in <a class="link" href="problems.html#ethereal1" title="Figure�39.1.�Starting a Capture.">Starting a Capture</a> snapshot. 72</p><p> 73A console version of ethereal is available as well and is called <code class="literal">tethereal</code>. 74</p><div class="figure"><a name="ethereal2"></a><p class="title"><b>Figure�39.2.�Main Ethereal Data Window.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/ethereal2.png" alt="Main Ethereal Data Window."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2685190"></a>The Windows Network Monitor</h3></div></div></div><p> 75<a class="indexterm" name="id2685198"></a> 76<a class="indexterm" name="id2685205"></a> 77<a class="indexterm" name="id2685212"></a> 78<a class="indexterm" name="id2685219"></a> 79<a class="indexterm" name="id2685226"></a> 80<a class="indexterm" name="id2685233"></a> 81For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer 82Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS 83allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous 84mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the 85local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted 86files. 87</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685250"></a>Installing Network Monitor on an NT Workstation</h4></div></div></div><p> 88<a class="indexterm" name="id2685258"></a> 89Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for 90installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT 91Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will 92need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD. 93</p><p> 94<a class="indexterm" name="id2685282"></a> 95Initially you will need to install <span class="application">Network Monitor Tools and Agent</span> 96on the NT Server to do this: 97</p><div class="itemizedlist"><ul type="disc"><li><p>Go to <span class="guibutton">Start</span> -> <span class="guibutton">Settings</span> -> <span class="guibutton">Control Panel</span> -> 98 <span class="guibutton">Network</span> -> <span class="guibutton">Services</span> -> <span class="guibutton">Add</span>.</p></li><li><p>Select the <span class="guilabel">Network Monitor Tools and Agent</span> and click on <span class="guibutton">OK</span>.</p></li><li><p>Click on <span class="guibutton">OK</span> on the Network Control Panel.</p></li><li><p>Insert the Windows NT Server 4.0 install CD when prompted.</p></li></ul></div><p> 99At this point, the Netmon files should exist in <code class="filename">%SYSTEMROOT%\System32\netmon\*.*</code>. 100Two subdirectories exist as well: <code class="filename">parsers\</code>, which contains the necessary DLLs 101for parsing the Netmon packet dump, and <code class="filename">captures\</code>. 102</p><p> 103To install the Netmon tools on an NT Workstation, you will first need to install the 104Network Monitor Agent from the Workstation install CD. 105</p><div class="itemizedlist"><ul type="disc"><li><p>Go to <span class="guibutton">Start</span> -> <span class="guibutton">Settings</span> -> 106 <span class="guibutton">Control Panel</span> -> <span class="guibutton">Network</span> -> 107 <span class="guibutton">Services</span> -> <span class="guibutton">Add</span>.</p></li><li><p>Select the <span class="guilabel">Network Monitor Agent</span>, click on 108 <span class="guibutton">OK</span>.</p></li><li><p>Click on <span class="guibutton">OK</span> in the Network Control Panel. 109 </p></li><li><p>Insert the Windows NT Workstation 4.0 install CD when prompted.</p></li></ul></div><p> 110Now copy the files from the NT Server in <code class="filename">%SYSTEMROOT%\System32\netmon</code> 111to <code class="filename">%SYSTEMROOT%\System32\netmon</code> on the workstation and set permissions 112as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon. 113</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2685500"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div></div><p> 114To install Netmon on Windows 9x/Me, install the Network Monitor Agent 115from the Windows 9x/Me CD (<code class="filename">\admin\nettools\netmon</code>). 116There is a readme file included with the Netmon driver files on the CD if you need 117information on how to do this. Copy the files from a working Netmon installation. 118</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685523"></a>Useful URLs</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at 119 <a class="ulink" href="http://www.skippy.net/linux/smb-howto.html" target="_top"> 120 http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>FTP site for older SMB specs, 121 <a class="ulink" href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top"> 122 ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685560"></a>Getting Mailing List Help</h2></div></div></div><p> 123There are a number of Samba-related mailing lists. Go to <a class="ulink" href="http://samba.org" target="_top">http://samba.org</a>, click on your nearest mirror, 124and then click on <code class="literal">Support</code>. Next, click on <code class="literal"> 125Samba-related mailing lists</code>. 126</p><p> 127For questions relating to Samba TNG, go to 128<a class="ulink" href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a>. 129It has been requested that you do not post questions about Samba-TNG to the 130mainstream Samba lists.</p><p> 131If you do post a message to one of the lists, please observe the following guidelines: 132</p><div class="itemizedlist"><ul type="disc"><li><p> 133<a class="indexterm" name="id2685616"></a> 134 Always remember that the developers are volunteers; they are 135 not paid and they never guarantee to produce a particular feature at 136 a particular time. Any timelines are “<span class="quote">best guess,</span>” and nothing more. 137 </p></li><li><p> 138<a class="indexterm" name="id2685634"></a> 139 Always mention what version of Samba you are using and what 140 operating system it's running under. You should list the relevant sections of 141 your <code class="filename">smb.conf</code> file, at least the options in <em class="parameter"><code>[global]</code></em> 142 that affect PDC support. 143 </p></li><li><p>In addition to the version, if you obtained Samba via 144 CVS, mention the date when you last checked it out.</p></li><li><p> Try to make your questions clear and brief. Lots of long, 145 convoluted questions get deleted before they are completely read! 146 Do not post HTML-encoded messages. Most people on mailing lists simply delete 147 them. 148 </p></li><li><p> If you run one of those nifty “<span class="quote">I'm on holiday</span>” things when 149 you are away, make sure its configured to not answer mailing list traffic. Autoresponses 150 to mailing lists really irritate the thousands of people who end up having to deal 151 with such bad netiquet bahavior. 152 </p></li><li><p> 153<a class="indexterm" name="id2685687"></a> 154 Don't cross post. Work out which is the best list to post to 155 and see what happens. Do not post to both samba-ntdom and samba-technical. 156 Many people active on the lists subscribe to more 157 than one list and get annoyed to see the same message two or more times. 158 Often someone who thinks a message would be better dealt 159 with on another list will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span> 160 log files written at a log level set to as much as 20. 161 Please do not send the entire log but just enough to give the context of the 162 error messages.</p></li><li><p>If you have a complete Netmon trace (from the opening of 163 the pipe to the error), you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email. 164 Consider pasting the relevant parts into the body of the message. The Samba 165 mailing lists go to a huge number of people. Do they all need a copy of your 166 <code class="filename">smb.conf</code> in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2685735"></a>How to Get Off the Mailing Lists</h2></div></div></div><p>To have your name removed from a Samba mailing list, go to the same 167place where you went to 168subscribe to it, go to <a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>, 169click on your nearest mirror, click on <code class="literal">Support</code>, and 170then click on <code class="literal">Samba-related mailing lists</code>. 171</p><p> 172Please do not post messages to the list asking to be removed. You will only 173be referred to the above address (unless that process failed in some way). 174</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="bugreport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�38.�The Samba Checklist�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�40.�Reporting Bugs</td></tr></table></div></body></html> 175
