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