diff options
Diffstat (limited to 'docs/htmldocs/problems.html')
| -rw-r--r-- | docs/htmldocs/problems.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html new file mode 100644 index 0000000000..41ec5ccbd2 --- /dev/null +++ b/docs/htmldocs/problems.html @@ -0,0 +1,135 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 34. Analyzing and Solving Samba Problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="diagnosis.html" title="Chapter 33. The Samba Checklist"><link rel="next" href="bugreport.html" title="Chapter 35. 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 34. 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 34. 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></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="problems.html#id2971255">Diagnostics Tools</a></dt><dd><dl><dt><a href="problems.html#id2971276">Debugging with Samba Itself</a></dt><dt><a href="problems.html#id2971441">Tcpdump</a></dt><dt><a href="problems.html#id2971477">Ethereal</a></dt><dt><a href="problems.html#id2971621">The Windows Network Monitor</a></dt></dl></dd><dt><a href="problems.html#id2971938">Useful URLs</a></dt><dt><a href="problems.html#id2971978">Getting Mailing List Help</a></dt><dt><a href="problems.html#id2972155">How to Get Off the Mailing Lists</a></dt></dl></div><p> +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="id2971255"></a>Diagnostics Tools</h2></div></div><div></div></div><p>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="id2971276"></a>Debugging with Samba Itself</h3></div></div><div></div></div><p> +One of the best diagnostic tools for debugging problems is Samba itself. +You 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 +<a class="indexterm" name="id2971308"></a><i class="parameter"><tt>debug level</tt></i> at which to run. +See the man pages for <b class="command">smbd, nmbd</b> and +<tt class="filename">smb.conf</tt> for more information regarding debugging options. The debug +level can range from 1 (the default) to 10 (100 for debugging passwords). +</p><p> +Another helpful method of debugging is to compile Samba using the +<b class="command">gcc -g </b> flag. This will include debug information in the binaries and +allow you to attach gdb to the running <b class="command">smbd/nmbd</b> process. +To attach <b class="command">gdb</b> to an <b class="command">smbd</b> +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 <i class="parameter"><tt>LsaEnumTrustedDomains</tt></i>. 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 <b class="command">ctrl-alt-delete</b> and actually +typing in your password, you can attach <b class="command">gdb</b> and continue. +</p><p> +Some useful Samba commands worth investigating are: +</p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>testparm | more</tt></b> +<tt class="prompt">$ </tt><b class="userinput"><tt>smbclient -L //{netbios name of server}</tt></b> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2971441"></a>Tcpdump</h3></div></div><div></div></div><p> +<ulink url="http://www.tcpdump.org/">Tcpdump</ulink> was the first +UNIX sniffer with SMB support. It is a command-line utility and +now, its SMB support is somewhat lagging that of <b class="command">ethereal</b> +and <b class="command">tethereal</b>. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2971477"></a>Ethereal</h3></div></div><div></div></div><p> +<ulink url="http://www.ethereal.com/">Ethereal</ulink> is a graphical +sniffer, available for both UNIX (Gtk) and Windows. Ethereal's +SMB support is quite good.</p><p>For details on the use of <b class="command">ethereal</b>, read the well-written +Ethereal User Guide.</p><div class="figure"><a name="ethereal1"></a><p class="title"><b>Figure 34.1. Starting a capture.</b></p><div class="mediaobject"><img src="projdoc/imagefiles/ethereal1.png" width="270" alt="Starting a capture."></div></div><p> +Listen for data on ports 137, 138, 139, and 445. For example, use the filter <b class="userinput"><tt>port 137, port 138, port 139, or port 445</tt></b> as seen in <link linkend="ethereal1">.</p><p>A console version of ethereal is available as well and is called +<b class="command">tethereal</b>.</p><div class="figure"><a name="ethereal2"></a><p class="title"><b>Figure 34.2. Main ethereal data window.</b></p><div class="mediaobject"><img src="projdoc/imagefiles/ethereal2.png" width="270" alt="Main ethereal data window."></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2971621"></a>The Windows Network Monitor</h3></div></div><div></div></div><p> +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="id2971641"></a>Installing Network Monitor on an NT Workstation</h4></div></div><div></div></div><p> +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> +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 <tt class="filename">%SYSTEMROOT%\System32\netmon\*.*</tt>. +Two subdirectories exist as well, <tt class="filename">parsers\</tt> which contains the necessary DLLs +for parsing the Netmon packet dump, and <tt class="filename">captures\</tt>. +</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 <tt class="filename">%SYSTEMROOT%\System32\netmon</tt> +to <tt class="filename">%SYSTEMROOT%\System32\netmon</tt> 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="id2971911"></a>Installing Network Monitor on Windows 9x/Me</h4></div></div><div></div></div><p> +To install Netmon on Windows 9x/Me, install the Network Monitor Agent +from the Windows 9x/Me CD (<tt class="filename">\admin\nettools\netmon</tt>). +There is a readme file located 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="id2971938"></a>Useful URLs</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at + <ulink url="http://www.skippy.net/linux/smb-howto.html"> + http://www.skippy.net/linux/smb-howto.html</ulink>. </p></li><li><p>FTP site for older SMB specs: + <ulink url="ftp://ftp.microsoft.com/developr/drg/CIFS/"> + ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2971978"></a>Getting Mailing List Help</h2></div></div><div></div></div><p> +There are a number of Samba-related mailing lists. Go to <ulink url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror +and then click on <b class="command">Support</b> and next click on <b class="command"> +Samba-related mailing lists</b>. +</p><p> +For questions relating to Samba TNG, go to +<ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/.</ulink> +It has been requested that you do not post questions about Samba-TNG to the +main-stream 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>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>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 <tt class="filename">smb.conf</tt> file, at least the options in <i class="parameter"><tt>[global]</tt></i> + 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 and 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 holidays</span>” things when + you are away, make sure its configured to not answer mailing list traffic. Auto-responses + to mailing lists really irritate the thousands of people who end up having to deal + with such bad netiquet bahavior. + </p></li><li><p>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 will see a message and thinking it 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 debug 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 + <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="id2972155"></a>How to Get Off the Mailing Lists</h2></div></div><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 <ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>, +click on your nearest mirror, click on <b class="command">Support</b> and +then click on<b class="command"> Samba related mailing lists</b>. +</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 33. 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 35. Reporting Bugs</td></tr></table></div></body></html> |