docs/htmldocs/problems.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
   2 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 28. Analysing and solving samba problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part IV. Troubleshooting"><link rel="previous" href="diagnosis.html" title="Chapter 27. The samba checklist"><link rel="next" href="bugreport.html" title="Chapter 29. 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 28. 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 IV. 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><h2 class="title"><a name="problems"></a>Chapter 28. Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&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">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&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">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="problems.html#id2902374">Diagnostics tools</a></dt><dt><a href="problems.html#id2903991">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="problems.html#id2904132">Useful URL's</a></dt><dt><a href="problems.html#id2904239">Getting help from the mailing lists</a></dt><dt><a href="problems.html#id2904392">How to get off the mailinglists</a></dt></dl></div><p>
   3 There are many sources of information available in the form
   4 of mailing lists, RFC's and documentation.  The docs that come
   5 with the samba distribution contain very good explanations of
   6 general SMB topics such as browsing.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2902374"></a>Diagnostics tools</h2></div></div><p>
   7 One of the best diagnostic tools for debugging problems is Samba itself.
   8 You can use the -d option for both smbd and nmbd to specify what
   9 'debug level' at which to run.  See the man pages on smbd, nmbd  and
  10 smb.conf for more information on debugging options.  The debug
  11 level can range from 1 (the default) to 10 (100 for debugging passwords).
  12 </p><p>
  13 Another helpful method of debugging is to compile samba using the
  14 <b>gcc -g </b> flag.   This will include debug
  15 information in the binaries and allow you to attach gdb to the
  16 running smbd / nmbd process.  In order to attach gdb to an smbd
  17 process for an NT workstation, first get the workstation to make the
  18 connection. Pressing ctrl-alt-delete and going down to the domain box
  19 is sufficient (at least, on the first time you join the domain) to
  20 generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
  21 maintains an open connection, and therefore there will be an smbd
  22 process running (assuming that you haven't set a really short smbd
  23 idle timeout)  So, in between pressing ctrl alt delete, and actually
  24 typing in your password, you can attach gdb and continue.
  25 </p><p>
  26 Some useful samba commands worth investigating:
  27 </p><div class="itemizedlist"><ul type="disc"><li><p>testparam | more</p></li><li><p>smbclient -L //{netbios name of server}</p></li></ul></div><p>
  28 An SMB enabled version of tcpdump is available from
  29 <a href="http://www.tcpdump.org/" target="_top">http://www.tcpdup.org/</a>.
  30 Ethereal, another good packet sniffer for Unix and Win32
  31 hosts, can be downloaded from <a href="http://www.ethereal.com/" target="_top">http://www.ethereal.com</a>.
  32 </p><p>
  33 For tracing things on the Microsoft Windows NT, Network Monitor
  34 (aka. netmon) is available on the Microsoft Developer Network CD's,
  35 the Windows NT Server install CD and the SMS CD's.  The version of
  36 netmon that ships with SMS allows for dumping packets between any two
  37 computers (i.e. placing the network interface in promiscuous mode).
  38 The version on the NT Server install CD will only allow monitoring
  39 of network traffic directed to the local NT box and broadcasts on the
  40 local subnet.  Be aware that Ethereal can read and write netmon
  41 formatted files.
  42 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903991"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</h2></div></div><p>
  43 Installing netmon on an NT workstation requires a couple
  44 of steps.  The following are for installing Netmon V4.00.349, which comes
  45 with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
  46 Workstation 4.0.  The process should be similar for other versions of
  47 Windows NT / Netmon.  You will need both the Microsoft Windows
  48 NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
  49 </p><p>
  50 Initially you will need to install 'Network Monitor Tools and Agent'
  51 on the NT Server.  To do this
  52 </p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
  53         Network - Services - Add </p></li><li><p>Select the 'Network Monitor Tools and Agent' and
  54         click on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
  55         </p></li><li><p>Insert the Windows NT Server 4.0 install CD
  56         when prompted.</p></li></ul></div><p>
  57 At this point the Netmon files should exist in
  58 <tt>%SYSTEMROOT%\System32\netmon\*.*</tt>.
  59 Two subdirectories exist as well, <tt>parsers\</tt>
  60 which contains the necessary DLL's for parsing the netmon packet
  61 dump, and <tt>captures\</tt>.
  62 </p><p>
  63 In order to install the Netmon tools on an NT Workstation, you will
  64 first need to install the 'Network  Monitor Agent' from the Workstation
  65 install CD.
  66 </p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
  67         Network - Services - Add</p></li><li><p>Select the 'Network Monitor Agent' and click
  68         on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
  69         </p></li><li><p>Insert the Windows NT Workstation 4.0 install
  70         CD when prompted.</p></li></ul></div><p>
  71 Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
  72 to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
  73 permissions as  you deem appropriate for your site. You will need
  74 administrative rights on the NT box to run netmon.
  75 </p><p>
  76 To install Netmon on a Windows 9x box install the network monitor agent
  77 from the Windows 9x CD (\admin\nettools\netmon).  There is a readme
  78 file located with the netmon driver files on the CD if you need
  79 information on how to do this.  Copy the files from a working
  80 Netmon installation.
  81 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904132"></a>Useful URL's</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>Home of Samba site <a href="http://samba.org" target="_top">
  82       http://samba.org</a>. We have a mirror near you !</p></li><li><p> The <span class="emphasis"><em>Development</em></span> document
  83 on the Samba mirrors might mention your problem. If so,
  84 it might mean that the developers are working on it.</p></li><li><p>See how Scott Merrill simulates a BDC behavior at
  85        <a href="http://www.skippy.net/linux/smb-howto.html" target="_top">
  86        http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>Although 2.0.7 has almost had its day as a PDC, David Bannon will
  87        keep the 2.0.7 PDC pages at <a href="http://bioserve.latrobe.edu.au/samba" target="_top">
  88        http://bioserve.latrobe.edu.au/samba</a> going for a while yet.</p></li><li><p>Misc links to CIFS information
  89        <a href="http://samba.org/cifs/" target="_top">http://samba.org/cifs/</a></p></li><li><p>NT Domains for Unix <a href="http://mailhost.cb1.com/~lkcl/ntdom/" target="_top">
  90        http://mailhost.cb1.com/~lkcl/ntdom/</a></p></li><li><p>FTP site for older SMB specs:
  91        <a href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top">
  92        ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904239"></a>Getting help from the mailing lists</h2></div></div><p>
  93 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
  94 and then click on <b>Support</b> and then click on <b>
  95 Samba related mailing lists</b>.
  96 </p><p>
  97 For questions relating to Samba TNG go to
  98 <a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a>
  99 It has been requested that you don't post questions about Samba-TNG to the
 100 main stream Samba lists.</p><p>
 101 If you post a message to one of the lists please observe the following guide lines :
 102 </p><div class="itemizedlist"><ul type="disc"><li><p> Always remember that the developers are volunteers, they are
 103 not paid and they never guarantee to produce a particular feature at
 104 a particular time. Any time lines are 'best guess' and nothing more.
 105 </p></li><li><p> Always mention what version of samba you are using and what
 106 operating system its running under. You should probably list the
 107 relevant sections of your <tt>smb.conf</tt> file, at least the options
 108 in [global] that affect PDC support.</p></li><li><p>In addition to the version, if you obtained Samba via
 109 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,
 110 convoluted questions get deleted before they are completely read !
 111 Don't post html encoded messages (if you can select colour or font
 112 size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when
 113 you are away, make sure its configured  to not answer mailing lists.
 114 </p></li><li><p> Don't cross post. Work out which is the best list to post to
 115 and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
 116 Many people active on the lists subscribe to more
 117 than one list and get annoyed to see the same message two or more times.
 118 Often someone will see a message and thinking it would be better dealt
 119 with on another, will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span>
 120 log files written at a debug level set to as much as 20.
 121 Please don't send the entire log but enough to give the context of the
 122 error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( from the opening of
 123 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.
 124 Consider pasting the relevant parts into the body of the message. The samba
 125 mailing lists go to a huge number of people, do they all need a copy of your
 126 smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904392"></a>How to get off the mailinglists</h2></div></div><p>To have your name removed from a samba mailing list, go to the
 127 same place you went to to get on it. Go to <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>,
 128 click on your nearest mirror and then click on <b>Support</b> and
 129 then click on <b> Samba related mailing lists</b>. Or perhaps see
 130 <a href="http://lists.samba.org/mailman/roster/samba-ntdom" target="_top">here</a>
 131 </p><p>
 132 Please don't post messages to the list asking to be removed, you will just
 133 be referred to the above address (unless that process failed in some way...)
 134 </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 27. 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 29. Reporting Bugs</td></tr></table></div></body></html>