[Table of Contents] [Previous]
[Next]
3.1. What are some diagnostics tools I can use to debug the domain
logon process and where can I find them?
- One of the best diagnostic tools for debugging problems is Samba itself. You can
use the -d option for both smbd and nmbd to specifiy what "debug" level 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 around 100 but
a debug level of about 20 will normally help you find any errors that samba is
encountering.
- Another helpful method of debugging is to compile samba using the gcc -g flag.
This will include debug information in the binaries and allow you to attch gdb to the
running smbd / nmbd process. In order to attach gdb to an smbd process for an NT
worksatation, 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 gdb attach and
continue.
- An SMB enabled version of tcpdump is available from ftp://samba.org/pub/samba/tcpdump-smb/
Capconvert is a small C
program for translating output from tcpdump-smb to CAP format that can be read by
netmon. You will need to use the raw output from tcp dump ( ie. tcpdump -w
output.dump ). Good news! Now you can convert Solaris' snoop output as well.
The C source code for snoop2cap
is available for download.
- 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 somes with SMS allows for dumping packets
between any two computers (ie. 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.
3.2. How do I install "Network Monitor" on an NT
Workstation or a Windows 9x box?
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
version of Windows NT / Netmon. You will need
- The Microsoft Windows NT Server 4.0 install CD.
- The Microsoft Windows NT Workstation 4.0 install CD.
Initially you will need to install "Network Monitor Tools and Agent" on the
NT Server. To do this
- Goto Start -> Settings -> Control Panel -> Network -> Services -> Add
- Select the "Network Monitor Tools and Agent" and click on "OK".
- Click "OK" on the Network Control Panel.
- Insert the Windows NT Server 4.0 install CD when prompted.
At this point the Netmon files should exist in %SYSTEMROOT%\System32\netmon\*.*
Two subdirectories exist as well, parsers\ which conatin the necessary DLL's for parsing
the netmon packet dump, and captures\.
In order to install the Netmon tools on an NT Workstation, you wil first need to
install the "Network Monitor Agent" from the Workstation install CD.
- Goto Start -> Settings -> Control Panel -> Network -> Services -> Add
- Select the "Network Monitor Agent" and click on "OK".
- Click "OK" on the Network Control Panel.
- Insert the Windows NT Worksatation 4.0 install CD when prompted.
Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* to
%SYSTEMROOT%\System32\netmon\*.* 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.
To install Netmon on a Windows 9x box
- install the network monitor agent from the Windows 9x CD (\admin\nettools\netmon).
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.
- Run netmon on Windows 9x :-)
3.3. I've seen the bits on the wire, but where can I find
out what it all means?
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.
- Mailing Lists :
- URL's
- RFC's
3.4. I've tried all the debugging help from question 3.1 and still
can't get things working. What information should I include in my posting to the
samba-ntdom mailing list?
If you post a problem regarding setting up samba PDC support to the samba-ntdom mailing
list, please include the following information
- The date when you last checked out the main code via cvs.
- The OS and version of the server on which you are running samba.
- The relavent sections of your smb.conf file. At least the options in [global] that
affect PDC support.
- Partial log files written at a debug level of at least 20. Please don't send
the entire log but enough to give the context of the error messages.
- If you have a complete netmon trace ( from the opening of the pipe to the error ) you
can send the *.CAP file as well.
[Table of Contents] [Previous]
[Next]
This FAQ is maintained by Jerry
Carter E-mail comments / suggestions jerry@samba.org
All trademarks are the sole property of their respective owners.