| 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.75.2"><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" title="Chapter 39. Analyzing and Solving Samba Problems"><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="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="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="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="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#id446780">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id446829">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id447073">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id447122">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id447261">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id447567">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id447602">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id447756">How to Get Off the Mailing Lists</a></span></dt></dl></div><p>
|
|---|
| 2 | <a class="indexterm" name="id446757"></a>
|
|---|
| 3 | <a class="indexterm" name="id446764"></a>
|
|---|
| 4 | <a class="indexterm" name="id446770"></a>
|
|---|
| 5 | There are many sources of information available in the form of mailing lists, RFCs, and documentation. The
|
|---|
| 6 | documentation that comes with the Samba distribution contains good explanations of general SMB topics such as
|
|---|
| 7 | browsing.
|
|---|
| 8 | </p><div class="sect1" title="Diagnostics Tools"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id446780"></a>Diagnostics Tools</h2></div></div></div><p>
|
|---|
| 9 | <a class="indexterm" name="id446788"></a>
|
|---|
| 10 | <a class="indexterm" name="id446795"></a>
|
|---|
| 11 | <a class="indexterm" name="id446802"></a>
|
|---|
| 12 | <a class="indexterm" name="id446808"></a>
|
|---|
| 13 | <a class="indexterm" name="id446815"></a>
|
|---|
| 14 | With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself
|
|---|
| 15 | provides 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,
|
|---|
| 17 | and displays it on the screen.
|
|---|
| 18 | </p><div class="sect2" title="Debugging with Samba Itself"><div class="titlepage"><div><div><h3 class="title"><a name="id446829"></a>Debugging with Samba Itself</h3></div></div></div><p>
|
|---|
| 19 | <a class="indexterm" name="id446837"></a>
|
|---|
| 20 | <a class="indexterm" name="id446844"></a>
|
|---|
| 21 | <a class="indexterm" name="id446851"></a>
|
|---|
| 22 | <a class="indexterm" name="id446858"></a>
|
|---|
| 23 | <a class="indexterm" name="id446864"></a>
|
|---|
| 24 | <a class="indexterm" name="id446871"></a>
|
|---|
| 25 | <a class="indexterm" name="id446878"></a>
|
|---|
| 26 | One of the best diagnostic tools for debugging problems is Samba itself. You can use the <code class="option">-d
|
|---|
| 27 | option</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.
|
|---|
| 28 | See the man pages for <code class="literal">smbd, nmbd</code>, and <code class="filename">smb.conf</code> for more information regarding debugging
|
|---|
| 29 | options. 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="id446929"></a>
|
|---|
| 32 | <a class="indexterm" name="id446936"></a>
|
|---|
| 33 | <a class="indexterm" name="id446943"></a>
|
|---|
| 34 | <a class="indexterm" name="id446950"></a>
|
|---|
| 35 | <a class="indexterm" name="id446957"></a>
|
|---|
| 36 | <a class="indexterm" name="id446963"></a>
|
|---|
| 37 | <a class="indexterm" name="id446970"></a>
|
|---|
| 38 | Another helpful method of debugging is to compile Samba using the <code class="literal">gcc -g </code> flag. This will
|
|---|
| 39 | include 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
|
|---|
| 41 | for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going
|
|---|
| 42 | down 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
|
|---|
| 44 | there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout). So, in
|
|---|
| 45 | between 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>
|
|---|
| 48 | Some useful Samba commands worth investigating are:
|
|---|
| 49 | <a class="indexterm" name="id447032"></a>
|
|---|
| 50 | <a class="indexterm" name="id447038"></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" title="Tcpdump"><div class="titlepage"><div><div><h3 class="title"><a name="id447073"></a>Tcpdump</h3></div></div></div><p>
|
|---|
| 56 | <a class="indexterm" name="id447081"></a>
|
|---|
| 57 | <a class="indexterm" name="id447088"></a>
|
|---|
| 58 | <a class="indexterm" name="id447095"></a>
|
|---|
| 59 | <a class="ulink" href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first
|
|---|
| 60 | UNIX sniffer with SMB support. It is a command-line utility and
|
|---|
| 61 | now, its SMB support is somewhat lagging that of <code class="literal">ethereal</code>
|
|---|
| 62 | and <code class="literal">tethereal</code>.
|
|---|
| 63 | </p></div><div class="sect2" title="Ethereal"><div class="titlepage"><div><div><h3 class="title"><a name="id447122"></a>Ethereal</h3></div></div></div><p>
|
|---|
| 64 | <a class="indexterm" name="id447130"></a>
|
|---|
| 65 | <a class="ulink" href="http://www.ethereal.com/" target="_top">Ethereal</a> is a graphical sniffer, available for both UNIX (Gtk)
|
|---|
| 66 | and Windows. Ethereal's SMB support is quite good. For details on the use of <code class="literal">ethereal</code>, read
|
|---|
| 67 | the 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="id447191"></a>
|
|---|
| 70 | Listen for data on ports 137, 138, 139, and 445. For example, use the filter <strong class="userinput"><code>port 137, port 138,
|
|---|
| 71 | port 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>
|
|---|
| 73 | A 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" title="The Windows Network Monitor"><div class="titlepage"><div><div><h3 class="title"><a name="id447261"></a>The Windows Network Monitor</h3></div></div></div><p>
|
|---|
| 75 | <a class="indexterm" name="id447269"></a>
|
|---|
| 76 | <a class="indexterm" name="id447276"></a>
|
|---|
| 77 | <a class="indexterm" name="id447283"></a>
|
|---|
| 78 | <a class="indexterm" name="id447290"></a>
|
|---|
| 79 | <a class="indexterm" name="id447296"></a>
|
|---|
| 80 | <a class="indexterm" name="id447303"></a>
|
|---|
| 81 | For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer
|
|---|
| 82 | Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS
|
|---|
| 83 | allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous
|
|---|
| 84 | mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the
|
|---|
| 85 | local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted
|
|---|
| 86 | files.
|
|---|
| 87 | </p><div class="sect3" title="Installing Network Monitor on an NT Workstation"><div class="titlepage"><div><div><h4 class="title"><a name="id447316"></a>Installing Network Monitor on an NT Workstation</h4></div></div></div><p>
|
|---|
| 88 | <a class="indexterm" name="id447324"></a>
|
|---|
| 89 | Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for
|
|---|
| 90 | installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
|
|---|
| 91 | Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will
|
|---|
| 92 | need 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="id447337"></a>
|
|---|
| 95 | Initially you will need to install <span class="application">Network Monitor Tools and Agent</span>
|
|---|
| 96 | on the NT Server to do this:
|
|---|
| 97 | </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><p>Select the <span class="guilabel">Network Monitor Tools and Agent</span> and click on <span class="guibutton">OK</span>.</p></li><li class="listitem"><p>Click on <span class="guibutton">OK</span> on the Network Control Panel.</p></li><li class="listitem"><p>Insert the Windows NT Server 4.0 install CD when prompted.</p></li></ul></div><p>
|
|---|
| 99 | At this point, the Netmon files should exist in <code class="filename">%SYSTEMROOT%\System32\netmon\*.*</code>.
|
|---|
| 100 | Two subdirectories exist as well: <code class="filename">parsers\</code>, which contains the necessary DLLs
|
|---|
| 101 | for parsing the Netmon packet dump, and <code class="filename">captures\</code>.
|
|---|
| 102 | </p><p>
|
|---|
| 103 | To install the Netmon tools on an NT Workstation, you will first need to install the
|
|---|
| 104 | Network Monitor Agent from the Workstation install CD.
|
|---|
| 105 | </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><p>Select the <span class="guilabel">Network Monitor Agent</span>, click on
|
|---|
| 108 | <span class="guibutton">OK</span>.</p></li><li class="listitem"><p>Click on <span class="guibutton">OK</span> in the Network Control Panel.
|
|---|
| 109 | </p></li><li class="listitem"><p>Insert the Windows NT Workstation 4.0 install CD when prompted.</p></li></ul></div><p>
|
|---|
| 110 | Now copy the files from the NT Server in <code class="filename">%SYSTEMROOT%\System32\netmon</code>
|
|---|
| 111 | to <code class="filename">%SYSTEMROOT%\System32\netmon</code> on the workstation and set permissions
|
|---|
| 112 | as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon.
|
|---|
| 113 | </p></div><div class="sect3" title="Installing Network Monitor on Windows 9x/Me"><div class="titlepage"><div><div><h4 class="title"><a name="id447546"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div></div><p>
|
|---|
| 114 | To install Netmon on Windows 9x/Me, install the Network Monitor Agent
|
|---|
| 115 | from the Windows 9x/Me CD (<code class="filename">\admin\nettools\netmon</code>).
|
|---|
| 116 | There is a readme file included with the Netmon driver files on the CD if you need
|
|---|
| 117 | information on how to do this. Copy the files from a working Netmon installation.
|
|---|
| 118 | </p></div></div></div><div class="sect1" title="Useful URLs"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447567"></a>Useful URLs</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><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" title="Getting Mailing List Help"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447602"></a>Getting Mailing List Help</h2></div></div></div><p>
|
|---|
| 123 | There 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,
|
|---|
| 124 | and then click on <code class="literal">Support</code>. Next, click on <code class="literal">
|
|---|
| 125 | Samba-related mailing lists</code>.
|
|---|
| 126 | </p><p>
|
|---|
| 127 | For 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>.
|
|---|
| 129 | It has been requested that you do not post questions about Samba-TNG to the
|
|---|
| 130 | mainstream Samba lists.</p><p>
|
|---|
| 131 | If you do post a message to one of the lists, please observe the following guidelines:
|
|---|
| 132 | </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
|
|---|
| 133 | <a class="indexterm" name="id447654"></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">“<span class="quote">best guess,</span>”</span> and nothing more.
|
|---|
| 137 | </p></li><li class="listitem"><p>
|
|---|
| 138 | <a class="indexterm" name="id447670"></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 class="listitem"><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 class="listitem"><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 class="listitem"><p> If you run one of those nifty <span class="quote">“<span class="quote">I'm on holiday</span>”</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 class="listitem"><p>
|
|---|
| 153 | <a class="indexterm" name="id447716"></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 class="listitem"><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 class="listitem"><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 class="listitem"><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" title="How to Get Off the Mailing Lists"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id447756"></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
|
|---|
| 167 | place where you went to
|
|---|
| 168 | subscribe to it, go to <a class="ulink" href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>,
|
|---|
| 169 | click on your nearest mirror, click on <code class="literal">Support</code>, and
|
|---|
| 170 | then click on <code class="literal">Samba-related mailing lists</code>.
|
|---|
| 171 | </p><p>
|
|---|
| 172 | Please do not post messages to the list asking to be removed. You will only
|
|---|
| 173 | be 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>
|
|---|
