| 1 |
rane 05/10/09 11:26:57 |
| 2 |
|
| 3 |
Added: xml/htdocs/doc/en/articles samba-p1.xml |
| 4 |
Log: |
| 5 |
first article from #106233, disclaimers test |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/doc/en/articles/samba-p1.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/samba-p1.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/samba-p1.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 12 |
|
| 13 |
Index: samba-p1.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="UTF-8"?> |
| 16 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 17 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/samba-p1.xml,v 1.1 2005/10/09 11:26:57 rane Exp $ --> |
| 18 |
|
| 19 |
<guide link="/doc/en/articles/samba-p1.xml" disclaimer="articles"> |
| 20 |
<title>Introduction to Samba, Part 1</title> |
| 21 |
|
| 22 |
<author title="Author"> |
| 23 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 24 |
</author> |
| 25 |
<!-- <author title="Editor"> |
| 26 |
<mail link="jackdark@×××××.com">Joshua Saddler</mail> |
| 27 |
</author> --> |
| 28 |
|
| 29 |
<abstract> |
| 30 |
Samba is an incredible tool for anyone who uses both Unix and Windows. By |
| 31 |
implementing the SMB/CIFS protocol for Unix, Samba allows Unix systems to share |
| 32 |
their resources with standard Windows clients. In this introductory article, |
| 33 |
Daniel Robbins introduces you to what Samba can do. The focus will be on key |
| 34 |
concepts. (He'll step you through the setup process in his next article.) By the |
| 35 |
end of this article, you'll have a good understanding of what Samba does, and |
| 36 |
how it goes about doing it. |
| 37 |
</abstract> |
| 38 |
|
| 39 |
<!-- The original version of this article was first published on IBM |
| 40 |
developerWorks, and is property of Westtech Information Services. This document |
| 41 |
is an updated version of the original article, and contains various improvements |
| 42 |
made by the Gentoo Linux Documentation team --> |
| 43 |
|
| 44 |
<version>1.0</version> |
| 45 |
<date>2005-10-06</date> |
| 46 |
|
| 47 |
<chapter> |
| 48 |
<title>Key concepts</title> |
| 49 |
<section> |
| 50 |
<title>Show me Samba</title> |
| 51 |
<body> |
| 52 |
|
| 53 |
<p> |
| 54 |
First, I'm going to show you a bunch of screenshots from one of my Windows NT |
| 55 |
boxes named kompressor. These screenshots demonstrate what a fully-configured |
| 56 |
Samba system looks like from the Windows side. They'll give you a real-world |
| 57 |
grasp of what Samba can do. |
| 58 |
</p> |
| 59 |
|
| 60 |
<p> |
| 61 |
I currently have three machines set up on my internal LAN: |
| 62 |
</p> |
| 63 |
|
| 64 |
<ul> |
| 65 |
<li><b>ntbox</b> (a Windows NT Workstation)</li> |
| 66 |
<li><b>freebox</b> (a FreeBSD server)</li> |
| 67 |
<li> |
| 68 |
<b>kompressor</b> (the Windows NT Workstation that I use as my primary |
| 69 |
desktop) |
| 70 |
</li> |
| 71 |
</ul> |
| 72 |
|
| 73 |
<p> |
| 74 |
In this environment, I use Samba extensively to share files, print, and even run |
| 75 |
Windows applications directly from freebox (Unix). Here's a screenshot showing |
| 76 |
the contents of kompressor's Network Neighborhood: |
| 77 |
</p> |
| 78 |
|
| 79 |
<figure link="/images/docs/l-samba-1.gif" caption="kompressor's Network |
| 80 |
Neighborhood"/> |
| 81 |
|
| 82 |
<p> |
| 83 |
As you can see, both ntbox and kompressor are visible, which is no surprise |
| 84 |
since they are both NT Workstations. What is rather unusual, however, is the |
| 85 |
fact that I can see freebox as well. Because freebox is running Samba, I can |
| 86 |
see it under Network Neighborhood on every Windows machinethat is part of my |
| 87 |
"GENTOO" Windows workgroup. |
| 88 |
</p> |
| 89 |
|
| 90 |
<p> |
| 91 |
Now it's time to take a look at what's "inside" freebox. The following window |
| 92 |
pops up after double-clicking on the freebox icon: |
| 93 |
</p> |
| 94 |
|
| 95 |
<figure link="/images/docs/l-samba-2.gif" caption="SMB/CIFS shares |
| 96 |
on freebox"/> |
| 97 |
|
| 98 |
<p> |
| 99 |
In this window you can see a bunch of what are called "shares". More |
| 100 |
specifically, they're called SMB/CIFS shares and contain parts of freebox's file |
| 101 |
system that are accessible through the network. |
| 102 |
</p> |
| 103 |
|
| 104 |
<note> |
| 105 |
I should mention that SMB stands for Server Message Block, the original name for |
| 106 |
the protocol used to share files on Windows. CIFS stands for the Common Internet |
| 107 |
File System, Microsoft's new acronym describing the more recent version of this |
| 108 |
protocol. |
| 109 |
</note> |
| 110 |
|
| 111 |
<p> |
| 112 |
On freebox, Samba has been specifically configured to create only those |
| 113 |
particular shares that you see above. The drobbins share contains the contents |
| 114 |
of my home directory. I like to store all my files on freebox (under Unix) to |
| 115 |
keep things centralized and easy to manage. One of the wonderful things about |
| 116 |
Samba is that it allows administrators to centralize the storage of user files |
| 117 |
rather than providing each user with two separate file locations for Windows and |
| 118 |
Unix. |
| 119 |
</p> |
| 120 |
|
| 121 |
</body> |
| 122 |
</section> |
| 123 |
<section> |
| 124 |
<title>Samba printing</title> |
| 125 |
<body> |
| 126 |
|
| 127 |
<p> |
| 128 |
In addition to standard shares (which act as virtual directories), you can also |
| 129 |
see a printer share called nec. Another really great feature of Samba is that |
| 130 |
you can share printers the same way you can from any Windows machine. Nec is my |
| 131 |
NEC SuperScript 870 laser printer, which is hooked up to freebox and set up as a |
| 132 |
standard Unix lpd-based printer. Samba allows this printer to be used by Windows |
| 133 |
clients just like a standard Windows network printer would. |
| 134 |
</p> |
| 135 |
|
| 136 |
<p> |
| 137 |
You may be wondering how the printer driver situation is handled since the |
| 138 |
printer is running under Unix. Good question. On freebox, nec is set up as a |
| 139 |
standard, parallel port-based printer running in "raw" mode. In other words, any |
| 140 |
print jobs sent to nec are handed directly to the printer as is, without any |
| 141 |
filtering or data massaging. |
| 142 |
</p> |
| 143 |
|
| 144 |
<p> |
| 145 |
On kompressor, nec is configured as an NEC SuperScript 870 network printer. When |
| 146 |
I print to it, the local NT printer driver generates the appropriate binary data |
| 147 |
for nec, which is then automatically spooled over the network to Samba running |
| 148 |
on freebox. Samba then automatically inserts this data untouched into nec's |
| 149 |
queue, and my printer begins printing the job. |
| 150 |
</p> |
| 151 |
|
| 152 |
<p> |
| 153 |
I should note that unfortunately my NEC SuperScript 870 is not a Postscript |
| 154 |
printer; it uses Adobe's proprietary PrintGear technology. While my printer is |
| 155 |
not fully supported under Unix, it still works perfectly when printing from |
| 156 |
Windows (this is because all the printer-specific data is generated on the |
| 157 |
Windows side, using the Windows driver). Ironically, since GhostScript (a |
| 158 |
freely-available PostScript-compatible interpreter available for Unix) does not |
| 159 |
know how to produce PrintGear output, I can only print plain ASCII text or 300 |
| 160 |
dpi PCL4-based documents from the Unix side; but from the Windows side, the |
| 161 |
Windows NT driver allows me to print at a full 600 dpi. I don't find this |
| 162 |
cumbersome at the moment because I do most of my printing from Windows. Although |
| 163 |
in the future it would be nice to have a printer that has Postscript built-in so |
| 164 |
that I can use the printer's full functionality from Unix as well. |
| 165 |
</p> |
| 166 |
|
| 167 |
</body> |
| 168 |
</section> |
| 169 |
<section> |
| 170 |
<title>Samba shares</title> |
| 171 |
<body> |
| 172 |
|
| 173 |
<p> |
| 174 |
OK, now it's time to move on to the next screen shot. This one illustrates the |
| 175 |
contents of the drobbins share on freebox, which is configured to share my Unix |
| 176 |
home directory. All the files listed in the window actually reside on freebox |
| 177 |
but are directly accessible from my Windows NT client machines. Being able to |
| 178 |
integrate Windows and Unix is wonderful stuff! |
| 179 |
</p> |
| 180 |
|
| 181 |
<figure link="/images/docs/l-samba-3.gif" caption="My home |
| 182 |
directory on freebox, accessed from kompressor"/> |
| 183 |
|
| 184 |
</body> |
| 185 |
</section> |
| 186 |
<section> |
| 187 |
<title>Understanding Samba</title> |
| 188 |
<body> |
| 189 |
|
| 190 |
<p> |
| 191 |
To show you more about how Samba works internally, I'm going to give you a very |
| 192 |
simplified explanation of what happened behind the scenes when I poked around in |
| 193 |
the Network Neighborhood. I should first explain something about my current |
| 194 |
Windows session. Since I am running Windows NT Workstation, I had to log in to |
| 195 |
gain access to the machine. For this NT session I logged in to the local machine |
| 196 |
with the username "Administrator" and the password "mypass". If I were running |
| 197 |
Windows 95 or 98, the standard Windows networking drivers would have asked me |
| 198 |
for a username or password as well. Under Windows 95 and 98, this password isn't |
| 199 |
really used to determine who can access the local machine; rather, it is cached |
| 200 |
and used to connect to network resources. |
| 201 |
</p> |
| 202 |
|
| 203 |
<p> |
| 204 |
Of course, Windows NT is extremely secure compared to Windows 95 and 98 and will |
| 205 |
not allow you to use the machine unless you supply a valid username and |
| 206 |
password. After kompressor validated my username and password against its local |
| 207 |
security database, it allowed me to begin using Windows. Kompressor will also |
| 208 |
use my username and password to try to automatically authenticate itself when I |
| 209 |
connect to password-protected network resources. |
| 210 |
</p> |
| 211 |
|
| 212 |
</body> |
| 213 |
</section> |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
-- |
| 218 |
gentoo-doc-cvs@g.o mailing list |
Archives