summaryrefslogtreecommitdiff
path: root/docs/htmldocs/problems.html
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2003-08-15 18:26:34 +0000
committerJelmer Vernooij <jelmer@samba.org>2003-08-15 18:26:34 +0000
commitd069dacb6e17866dd5d3862e1837a9cae008644f (patch)
treec1b660005d31583819c7f43f79168a3332150a85 /docs/htmldocs/problems.html
parentcedd66b6e67f4c463eaa072f0e6d87ee1f55718e (diff)
downloadsamba-d069dacb6e17866dd5d3862e1837a9cae008644f.tar.gz
samba-d069dacb6e17866dd5d3862e1837a9cae008644f.tar.bz2
samba-d069dacb6e17866dd5d3862e1837a9cae008644f.zip
Regenerate docs
(This used to be commit dc33e94161e4fc1ca6bf66a321c708c89bb276e3)
Diffstat (limited to 'docs/htmldocs/problems.html')
-rw-r--r--docs/htmldocs/problems.html138
1 files changed, 138 insertions, 0 deletions
diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html
new file mode 100644
index 0000000000..24ddc7c02c
--- /dev/null
+++ b/docs/htmldocs/problems.html
@@ -0,0 +1,138 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 34. Analysing 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="samba-doc.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. Analysing 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. Analysing 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">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</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">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</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">&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</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#id2959747">Diagnostics tools</a></dt><dd><dl><dt><a href="problems.html#id2959768">Debugging with Samba itself</a></dt><dt><a href="problems.html#id2959894">Tcpdump</a></dt><dt><a href="problems.html#id2959915">Ethereal</a></dt><dt><a href="problems.html#id2959968">The Windows Network Monitor</a></dt></dl></dd><dt><a href="problems.html#id2960285">Useful URLs</a></dt><dt><a href="problems.html#id2960326">Getting help from the mailing lists</a></dt><dt><a href="problems.html#id2960484">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, RFC's and documentation. The docs that come
+with the samba distribution contain very 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="id2959747"></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, analyses 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="id2959768"></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 what
+<a class="indexterm" name="id2959799"></a><i class="parameter"><tt>debug level</tt></i> at which to run. See the man pages on smbd, nmbd and
+smb.conf for more information on 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="userinput"><tt>gcc -g </tt></b> flag. This will include debug
+information in the binaries and allow you to attach gdb to the
+running smbd / nmbd process. In order to attach gdb to an smbd
+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, on the first time you join the domain) to
+generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
+maintains an open connection, and therefore there will be an smbd
+process running (assuming that you haven't set a really short smbd
+idle timeout) So, in between pressing ctrl alt delete, and actually
+typing in your password, you can attach gdb and continue.
+</p><p>
+Some useful samba commands worth investigating:
+</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="id2959894"></a>Tcpdump</h3></div></div><div></div></div><p><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
+nowadays, it's SMB support is somewhat less then that of ethereal
+and tethereal.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959915"></a>Ethereal</h3></div></div><div></div></div><p>
+<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 very good.</p><p>For details on the use of ethereal, read the well-written
+ethereal User Guide.</p><p>
+Listen for data on ports 137, 138, 139 and 445. E.g.
+use the filter <b class="userinput"><tt>port 137 or port 138 or port 139 or port 445</tt></b>.</p><p>A console version of ethereal is available as well and is called
+<b class="command">tethereal</b>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959968"></a>The Windows Network Monitor</h3></div></div><div></div></div><p>
+For tracing things on the Microsoft Windows NT, Network Monitor
+(aka. netmon) is available on the Microsoft Developer Network CD's,
+the Windows NT Server install CD and the SMS CD's. 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="id2959989"></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 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 / 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>Goto <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 <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 DLL's for parsing the netmon packet
+dump, and <tt class="filename">captures\</tt>.
+</p><p>
+In order 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>Goto <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> and click
+ on <span class="guibutton">OK</span>.</p></li><li><p>Click <span class="guibutton">OK</span> on 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="id2960258"></a>Installing 'Network Monitor' on an 9x Workstation</h4></div></div><div></div></div><p>
+To install Netmon on a Windows 9x box install the network monitor agent
+from the Windows 9x 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="id2960285"></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
+ <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="id2960326"></a>Getting help from the mailing lists</h2></div></div><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 <b class="command">Support</b> and then click on <b class="command">
+Samba related mailing lists</b>.
+</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 don't post questions about Samba-TNG to the
+main stream Samba lists.</p><p>
+If you post a message to one of the lists please observe the following guide lines :
+</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 time lines are 'best guess' and nothing more.
+</p></li><li><p>Always mention what version of samba you are using and what
+operating system its running under. You should probably list the
+relevant sections of your <tt class="filename">smb.conf</tt> file, at least the options
+in [global] 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 question clear and brief, lots of long,
+convoluted questions get deleted before they are completely read !
+Don't post html encoded messages (if you can select colour or font
+size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when
+you are away, make sure its configured to not answer mailing lists.
+</p></li><li><p> Don't cross post. Work out which is the best list to post to
+and see what happens, i.e. don't 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, 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 don't send the entire log but enough to give the context of the
+error messages.</p></li><li><p>(Possibly) 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
+smb.conf 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="id2960484"></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 you went to to get on it. Go to <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>,
+click on your nearest mirror and then click on <b class="command">Support</b> and
+then click on <b class="command"> Samba related mailing lists</b>.
+</p><p>
+Please don't post messages to the list asking to be removed, you will just
+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="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 35. Reporting Bugs</td></tr></table></div></body></html>