diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/problems.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/problems.html | 174 |
1 files changed, 174 insertions, 0 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/problems.html b/docs/htmldocs/Samba3-HOWTO/problems.html new file mode 100644 index 0000000000..b0d0d92878 --- /dev/null +++ b/docs/htmldocs/Samba3-HOWTO/problems.html @@ -0,0 +1,174 @@ +<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.71.0"><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 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="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a 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 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 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 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#id440198">Diagnostics Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="problems.html#id440247">Debugging with Samba Itself</a></span></dt><dt><span class="sect2"><a href="problems.html#id440487">Tcpdump</a></span></dt><dt><span class="sect2"><a href="problems.html#id440536">Ethereal</a></span></dt><dt><span class="sect2"><a href="problems.html#id440675">The Windows Network Monitor</a></span></dt></dl></dd><dt><span class="sect1"><a href="problems.html#id440981">Useful URLs</a></span></dt><dt><span class="sect1"><a href="problems.html#id441016">Getting Mailing List Help</a></span></dt><dt><span class="sect1"><a href="problems.html#id441170">How to Get Off the Mailing Lists</a></span></dt></dl></div><p> +<a class="indexterm" name="id440175"></a> +<a class="indexterm" name="id440182"></a> +<a class="indexterm" name="id440188"></a> +There are many sources of information available in the form of mailing lists, RFCs, and documentation. The +documentation that comes with the Samba distribution contains good explanations of general SMB topics such as +browsing. +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id440198"></a>Diagnostics Tools</h2></div></div></div><p> +<a class="indexterm" name="id440206"></a> +<a class="indexterm" name="id440213"></a> +<a class="indexterm" name="id440219"></a> +<a class="indexterm" name="id440226"></a> +<a class="indexterm" name="id440233"></a> +With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself +provides rather useful information, but in some cases you might have to fall back to using a +<span class="emphasis"><em>sniffer</em></span>. A sniffer is a program that listens on your LAN, analyzes the data sent on it, +and displays it on the screen. +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id440247"></a>Debugging with Samba Itself</h3></div></div></div><p> +<a class="indexterm" name="id440255"></a> +<a class="indexterm" name="id440262"></a> +<a class="indexterm" name="id440268"></a> +<a class="indexterm" name="id440275"></a> +<a class="indexterm" name="id440282"></a> +<a class="indexterm" name="id440289"></a> +<a class="indexterm" name="id440296"></a> +One of the best diagnostic tools for debugging problems is Samba itself. You can use the <code class="option">-d +option</code> for both <span class="application">smbd</span> and <span class="application">nmbd</span> to specify the <a class="indexterm" name="id440319"></a>debug level at which to run. +See the man pages for <code class="literal">smbd, nmbd</code>, and <code class="filename">smb.conf</code> for more information regarding debugging +options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords). +</p><p> +<a class="indexterm" name="id440343"></a> +<a class="indexterm" name="id440350"></a> +<a class="indexterm" name="id440356"></a> +<a class="indexterm" name="id440363"></a> +<a class="indexterm" name="id440370"></a> +<a class="indexterm" name="id440376"></a> +<a class="indexterm" name="id440383"></a> +Another helpful method of debugging is to compile Samba using the <code class="literal">gcc -g </code> flag. This will +include debug information in the binaries and allow you to attach <code class="literal">gdb</code> to the running +<code class="literal">smbd/nmbd</code> process. To attach <code class="literal">gdb</code> to an <code class="literal">smbd</code> process +for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going +down to the domain box is sufficient (at least, the first time you join the domain) to generate a +<em class="parameter"><code>LsaEnumTrustedDomains</code></em>. Thereafter, the workstation maintains an open connection and +there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout). So, in +between pressing <code class="literal">ctrl-alt-delete</code> and actually typing in your password, you can attach +<code class="literal">gdb</code> and continue. +</p><p> +Some useful Samba commands worth investigating are: +<a class="indexterm" name="id440446"></a> +<a class="indexterm" name="id440452"></a> +</p><pre class="screen"> +<code class="prompt">$ </code><strong class="userinput"><code>testparm | more</code></strong> +<code class="prompt">$ </code><strong class="userinput"><code>smbclient -L //{netbios name of server}</code></strong> +</pre><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id440487"></a>Tcpdump</h3></div></div></div><p> +<a class="indexterm" name="id440495"></a> +<a class="indexterm" name="id440502"></a> +<a class="indexterm" name="id440508"></a> +<a href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first +UNIX sniffer with SMB support. It is a command-line utility and +now, its SMB support is somewhat lagging that of <code class="literal">ethereal</code> +and <code class="literal">tethereal</code>. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id440536"></a>Ethereal</h3></div></div></div><p> +<a class="indexterm" name="id440544"></a> +<a href="http://www.ethereal.com/" target="_top">Ethereal</a> is a graphical sniffer, available for both UNIX (Gtk) +and Windows. Ethereal's SMB support is quite good. For details on the use of <code class="literal">ethereal</code>, read +the well-written Ethereal User Guide. +</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> +<a class="indexterm" name="id440604"></a> +Listen for data on ports 137, 138, 139, and 445. For example, use the filter <strong class="userinput"><code>port 137, port 138, +port 139, or port 445</code></strong> as seen in <a href="problems.html#ethereal1" title="Figure 39.1. Starting a Capture.">Starting a Capture</a> snapshot. +</p><p> +A console version of ethereal is available as well and is called <code class="literal">tethereal</code>. +</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="id440675"></a>The Windows Network Monitor</h3></div></div></div><p> +<a class="indexterm" name="id440683"></a> +<a class="indexterm" name="id440690"></a> +<a class="indexterm" name="id440696"></a> +<a class="indexterm" name="id440703"></a> +<a class="indexterm" name="id440710"></a> +<a class="indexterm" name="id440717"></a> +For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer +Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS +allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous +mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the +local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted +files. +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id440730"></a>Installing Network Monitor on an NT Workstation</h4></div></div></div><p> +<a class="indexterm" name="id440738"></a> +Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for +installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT +Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will +need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD. +</p><p> +<a class="indexterm" name="id440751"></a> +Initially you will need to install <span class="application">Network Monitor Tools and Agent</span> +on the NT Server to do this: +</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> -> + <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> +At this point, the Netmon files should exist in <code class="filename">%SYSTEMROOT%\System32\netmon\*.*</code>. +Two subdirectories exist as well: <code class="filename">parsers\</code>, which contains the necessary DLLs +for parsing the Netmon packet dump, and <code class="filename">captures\</code>. +</p><p> +To install the Netmon tools on an NT Workstation, you will first need to install the +Network Monitor Agent from the Workstation install CD. +</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> -> <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. + </p></li><li><p>Insert the Windows NT Workstation 4.0 install CD when prompted.</p></li></ul></div><p> +Now copy the files from the NT Server in <code class="filename">%SYSTEMROOT%\System32\netmon</code> +to <code class="filename">%SYSTEMROOT%\System32\netmon</code> on the workstation and set permissions +as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon. +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id440960"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div></div><p> +To install Netmon on Windows 9x/Me, install the Network Monitor Agent +from the Windows 9x/Me CD (<code class="filename">\admin\nettools\netmon</code>). +There is a readme file included with the Netmon driver files on the CD if you need +information on how to do this. Copy the files from a working Netmon installation. +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id440981"></a>Useful URLs</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at + <a href="http://www.skippy.net/linux/smb-howto.html" target="_top"> + http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>FTP site for older SMB specs, + <a href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top"> + 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="id441016"></a>Getting Mailing List Help</h2></div></div></div><p> +There 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, +and then click on <code class="literal">Support</code>. Next, click on <code class="literal"> +Samba-related mailing lists</code>. +</p><p> +For questions relating to Samba TNG, go to +<a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a>. +It has been requested that you do not post questions about Samba-TNG to the +mainstream Samba lists.</p><p> +If you do post a message to one of the lists, please observe the following guidelines: +</p><div class="itemizedlist"><ul type="disc"><li><p> +<a class="indexterm" name="id441068"></a> + Always remember that the developers are volunteers; they are + not paid and they never guarantee to produce a particular feature at + a particular time. Any timelines are “<span class="quote">best guess,</span>” and nothing more. + </p></li><li><p> +<a class="indexterm" name="id441084"></a> + Always mention what version of Samba you are using and what + operating system it's running under. You should list the relevant sections of + your <code class="filename">smb.conf</code> file, at least the options in <em class="parameter"><code>[global]</code></em> + that affect PDC support. + </p></li><li><p>In addition to the version, if you obtained Samba via + 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, + convoluted questions get deleted before they are completely read! + Do not post HTML-encoded messages. Most people on mailing lists simply delete + them. + </p></li><li><p> If you run one of those nifty “<span class="quote">I'm on holiday</span>” things when + you are away, make sure its configured to not answer mailing list traffic. Autoresponses + to mailing lists really irritate the thousands of people who end up having to deal + with such bad netiquet bahavior. + </p></li><li><p> +<a class="indexterm" name="id441130"></a> + Don't cross post. Work out which is the best list to post to + and see what happens. Do not post to both samba-ntdom and samba-technical. + Many people active on the lists subscribe to more + than one list and get annoyed to see the same message two or more times. + Often someone who thinks a message would be better dealt + with on another list will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span> + log files written at a log level set to as much as 20. + Please do not send the entire log but just enough to give the context of the + error messages.</p></li><li><p>If you have a complete Netmon trace (from the opening of + 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. + Consider pasting the relevant parts into the body of the message. The Samba + mailing lists go to a huge number of people. Do they all need a copy of your + <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="id441170"></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 +place where you went to +subscribe to it, go to <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>, +click on your nearest mirror, click on <code class="literal">Support</code>, and +then click on <code class="literal">Samba-related mailing lists</code>. +</p><p> +Please do not post messages to the list asking to be removed. You will only +be referred to the above address (unless that process failed in some way). +</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> |