P. 1
Samba

Samba

|Views: 167|Likes:
Published by Nurul Istiqomah

More info:

Published by: Nurul Istiqomah on Dec 14, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

02/21/2014

pdf

text

original

Modularity is a large part of both product quality and ease of troubleshooting. Samba is
modular. The following is a simple block diagram of a Samba system:

smb.conf------->testparm

| |
V V
smb<----->network<----->nmbd<-->smbd<-------->unix
client | | filesystem
V V
log.nmb log.smb

The rest of this chapter refers to the preceding diagram as the Samba system block dia-
gram. It’s very simplified,but it’s very functional for the purpose of troubleshooting.

Because troubleshooting consists of dividing a system to narrow the scope of a root
cause,the modularity of Samba greatly eases troubleshooting.

Creating a Turnkey Samba System

PARTII

614

25 8628 CH22 3/17/00 1:14 PM Page 614

The Samba Troubleshooting Hierarchy

Referring to the Samba system block diagram,it’s evident Samba can be intercepted
before the network by accessing it on the server as localhost,using smbclientand
other utilities. If Samba doesn’t work locally,that’s the problem requiring a fix.

If Samba is accessed from the network,there are a number of different clients from
which it can be accessed. From a troubleshooting point of view,the smbclientprogram
is the most trustworthy client. The following is the Samba troubleshooting hierarchy:

1.Get it working on localhost.

2.Get it working over the wire from a Linux SMB client.

3.Get it working over the wire from a Windows command-line SMB client.

4.Get it working over the wire from a Windows graphical SMB client.

Step 1 bypasses the network for a reading on Samba alone.

Step 2 bypasses Windows clients,which often add problems of their own.

Step 3 bypasses Network Neighborhood and Windows Explorer,which typically are
more touchy than Windows command-line SMB clients such as the net useand net

viewcommands.

Step 4 tests the intended use of Samba.

Many times step 2 is bypassed,instead relying on step 1 to prove that Samba and nmbd
naming work and relying on pingcommands to prove network connectivity. That’s what

DIAGNOSIS.txtdoes. DIAGNOSIS.txtis a great example of a series of tests that logically
traverse the Samba troubleshooting hierarchy.

This hierarchy is used to narrow the scope of Samba problems,and it often proves the
problem is not even a Samba problem. For maximum troubleshooting productivity,the
Samba troubleshooting hierarchy must be consciously consulted in all Samba trou-
bleshooting activities.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->