• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /netgear-WNDR4500-V1.0.1.40_1.0.68/ap/gpl/samba-3.0.13/docs/htmldocs/Samba-HOWTO-Collection/
1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�40.�Samba and Other CIFS Clients</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part�VI.�Appendixes"><link rel="prev" href="Portability.html" title="Chapter�39.�Portability"><link rel="next" href="speed.html" title="Chapter�41.�Samba Performance Tuning"></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�40.�Samba and Other CIFS Clients</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Portability.html">Prev</a>�</td><th width="60%" align="center">Part�VI.�Appendixes</th><td width="20%" align="right">�<a accesskey="n" href="speed.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter�40.�Samba and Other CIFS Clients</h2></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">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:dan@samba.org">dan@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><span class="contrib">OS/2</span><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="Other-Clients.html#id2619867">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2619932">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2619938">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620062">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620114">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2620202">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2620208">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620291">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620317">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620364">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620391">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id2620406">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2620446">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id2620508">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id2620528">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id2620735">Windows NT 3.1</a></span></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619867"></a>Macintosh Clients</h2></div></div></div><p>
2Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> has a CIFS Client/Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE.</a>
3They test it against Windows 95, Windows NT /200x/XP and Samba for
4compatibility issues. At the time of this writing, DAVE was at version
54.1. Please refer to Thursby's Web site for more information regarding this
6product.
7</p><p> 
8Alternatives  There are two free implementations of AppleTalk for
9several kinds of UNIX machines and several more commercial ones.
10These products allow you to run file services and print services
11natively to Macintosh users, with no additional support required on
12the Macintosh. The two free implementations are 
13<a href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk,</a> and 
14<a href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP.</a> 
15What Samba offers MS Windows users, these packages offer to Macs. 
16For more info on these packages, Samba, and Linux (and other UNIX-based systems), see
17<a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html.</a>
18</p><p>Newer versions of the Macintosh (Mac OS X) include Samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619932"></a>OS2 Client</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619938"></a>Configuring OS/2 Warp Connect or OS/2 Warp 4</h3></div></div></div><p>Basically, you need three components:</p><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client (IBM Peer)</p></li><li><p>TCP/IP (Internet support) </p></li><li><p>The &#8220;<span class="quote"><span class="emphasis"><em>NetBIOS over TCP/IP</em></span></span>&#8221; driver (TCPBEUI)</p></li></ul></div><p>Installing the first two together with the base operating 
19		system on a blank system is explained in the Warp manual. If Warp 
20		has already been installed, but you now want to install the 
21		networking support, use the &#8220;<span class="quote"><span class="emphasis"><em>Selective Install for Networking</em></span></span>&#8221; 
22		object in the &#8220;<span class="quote"><span class="emphasis"><em>System Setup</em></span></span>&#8221; folder.</p><p>Adding the &#8220;<span class="quote"><span class="emphasis"><em>NetBIOS over TCP/IP</em></span></span>&#8221; driver is not described 
23		in the manual and just barely in the online documentation. Start 
24		<span><b class="command">MPTS.EXE</b></span>, click on <span class="guiicon">OK</span>, click on <span class="guimenu">Configure LAPS</span> and click 
25		on <span class="guimenu">IBM OS/2 NETBIOS OVER TCP/IP</span> in  <span class="guilabel">Protocols</span>. This line 
26		is then moved to <span class="guilabel">Current Configuration</span>. Select that line, 
27		click on <span class="guimenuitem">Change number</span> and increase it from 0 to 1. Save this
28		configuration.</p><p>If the Samba server is not on your local subnet, you 
29		can optionally add IP names and addresses of these servers 
30		to the <span class="guimenu">Names List</span>, or specify a  WINS server (NetBIOS 
31		Nameserver in IBM and RFC terminology). For Warp Connect, you 
32		may need to download an update for <tt class="constant">IBM Peer</tt> to bring it on 
33		the same level as Warp 4. See the Web page mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620062"></a>Configuring Other Versions of OS/2</h3></div></div></div><p>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</p><p>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is
34		available from 
35		<a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top">
36		ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>. In a nutshell, edit
37	the file <tt class="filename">\OS2VER</tt> in the root directory of the OS/2 boot partition and add the lines:</p><pre class="programlisting">
38		20=setup.exe
39		20=netwksta.sys
40		20=netvdd.sys
41		</pre><p>before you install the client. Also, do not use the included NE2000 driver because it is buggy.
42		Try the NE2000 or NS2000 driver from <a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top">
43 		ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead.
44		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620114"></a>Printer Driver Download for OS/2 Clients</h3></div></div></div><p>Create a share called <i class="parameter"><tt>[PRINTDRV]</tt></i> that is 
45		world-readable. Copy your OS/2 driver files there. The <tt class="filename">.EA_</tt>
46		files must still be separate, so you will need to use the original install files
47		and not copy an installed driver from an OS/2 system.</p><p>Install the NT driver first for that printer. Then, add to your <tt class="filename">smb.conf</tt> a parameter,
48		<a class="indexterm" name="id2620149"></a>os2 driver map. 
49		Next, in the file specified by <i class="replaceable"><tt>filename</tt></i>, map the 
50		name of the NT driver name to the OS/2 driver name as follows:</p><p><i class="parameter"><tt><i class="replaceable"><tt>nt driver name</tt></i> = <i class="replaceable"><tt>os2 driver name</tt></i>.<i class="replaceable"><tt>device name</tt></i></tt></i>, e.g.</p><p><i class="parameter"><tt>
51		HP LaserJet 5L = LASERJET.HP LaserJet 5L</tt></i></p><p>You can have multiple drivers mapped in this file.</p><p>If you only specify the OS/2 driver name, and not the 
52		device name, the first attempt to download the driver will 
53		actually download the files, but the OS/2 client will tell 
54		you the driver is not available. On the second attempt, it 
55		will work. This is fixed simply by adding the device name
56  		 to the mapping, after which it will work on the first attempt.
57		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620202"></a>Windows for Workgroups</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620208"></a>Latest TCP/IP Stack from Microsoft</h3></div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
58for Workgroups. The early TCP/IP stacks had lots of bugs.</p><p> 
59Microsoft has released an incremental upgrade to their TCP/IP 32-bit
60VxD drivers. The latest release can be found on their ftp site at
61ftp.microsoft.com, located in <tt class="filename">/Softlib/MSLFILES/TCP32B.EXE</tt>.
62There is an update.txt file there that describes the problems that were
63fixed. New files include <tt class="filename">WINSOCK.DLL</tt>, 
64<tt class="filename">TELNET.EXE</tt>, 
65<tt class="filename">WSOCK.386</tt>, 
66<tt class="filename">VNBT.386</tt>,
67<tt class="filename">WSTCP.386</tt>, 
68<tt class="filename">TRACERT.EXE</tt>, 
69<tt class="filename">NETSTAT.EXE</tt>, and 
70<tt class="filename">NBTSTAT.EXE</tt>.
71</p><p>More information about this patch is available in <a href="http://support.microsoft.com/kb/q99891/" target="_top">Knowledge base article 99891</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620291"></a>Delete .pwl Files After Password Change</h3></div></div></div><p>
72Windows for Workgroups does a lousy job with passwords. When you change passwords on either
73the UNIX box or the PC, the safest thing to do is to delete the .pwl files in the Windows
74directory. The PC will complain about not finding the files, but will soon get over it,
75allowing you to enter the new password.
76</p><p> 
77If you do not do this, you may find that Windows for Workgroups remembers and uses the old
78password, even if you told it a new one.
79</p><p> 
80Often Windows for Workgroups will totally ignore a password you give it in a dialog box.
81</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620317"></a>Configuring Windows for Workgroups Password Handling</h3></div></div></div><p>
82There is a program call <tt class="filename">admincfg.exe</tt>
83on the last disk (disk 8) of the WFW 3.11 disk set. To install it,
84type <b class="userinput"><tt>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</tt></b>.
85Then add an icon for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> Menu. 
86This program allows you to control how WFW handles passwords, i.e.,
87Disable Password Caching and so on.
88for use with <a class="indexterm" name="id2620355"></a>security = user.
89</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620364"></a>Password Case Sensitivity</h3></div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server.
90UNIX passwords can be case-sensitive though. Check the <tt class="filename">smb.conf</tt> information on
91<a class="indexterm" name="id2620380"></a>password level to specify what characters
92Samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620391"></a>Use TCP/IP as Default Protocol</h3></div></div></div><p>To support print queue reporting, you may find
93that you have to use TCP/IP as the default protocol under
94Windows for Workgroups. For some reason, if you leave NetBEUI as the default,
95it may break the print queue reporting on some systems.
96It is presumably a Windows for Workgroups bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620406"></a>Speed Improvement</h3></div></div></div><p>
97	Note that some people have found that setting <i class="parameter"><tt>DefaultRcvWindow</tt></i> in
98the <i class="parameter"><tt>[MSTCP]</tt></i> section of the 
99<tt class="filename">SYSTEM.INI</tt> file under Windows for Workgroups to 3072 gives a
100big improvement.
101</p><p>
102My own experience with DefaultRcvWindow is that I get a much better
103performance with a large value (16384 or larger). Other people have
104reported that anything over 3072 slows things down enormously. One
105person even reported a speed drop of a factor of 30 when he went from
1063072 to 8192.
107</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620446"></a>Windows 95/98</h2></div></div></div><p>
108When using Windows 95 OEM SR2, the following updates are recommended where Samba
109is being used. Please note that the above change will effect you once these
110updates  have been installed.
111</p><p> 
112There are more updates than the ones mentioned here. You are referred to the
113Microsoft Web site for all currently available updates to your specific version
114of Windows 95.
115</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Kernel Update: KRNLUPD.EXE</td></tr><tr><td>Ping Fix: PINGUPD.EXE</td></tr><tr><td>RPC Update: RPCRTUPD.EXE</td></tr><tr><td>TCP/IP Update: VIPUPD.EXE</td></tr><tr><td>Redirector Update: VRDRUPD.EXE</td></tr></table><p>
116Also, if using <span class="application">MS Outlook,</span> it is desirable to 
117install the <span><b class="command">OLEUPD.EXE</b></span> fix. This
118fix may stop your machine from hanging for an extended period when exiting
119Outlook and you may notice a significant speedup when accessing network
120neighborhood services.
121</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620508"></a>Speed Improvement</h3></div></div></div><p>
122Configure the Windows 95 TCP/IP registry settings to give better
123performance. I use a program called <span><b class="command">MTUSPEED.exe</b></span> that I got off the
124Internet. There are various other utilities of this type freely available.
125</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620528"></a>Windows 2000 Service Pack 2</h2></div></div></div><p> 
126There are several annoyances with Windows 2000 SP2. One of which
127only appears when using a Samba server to host user profiles
128to Windows 2000 SP2 clients in a Windows domain. This assumes
129that Samba is a member of the domain, but the problem will
130most likely occur if it is not.
131</p><p> 
132In order to serve profiles successfully to Windows 2000 SP2 
133clients (when not operating as a PDC), Samba must have 
134<a class="indexterm" name="id2620551"></a>nt acl support = no
135added to the file share which houses the roaming profiles.
136If this is not done, then the Windows 2000 SP2 client will
137complain about not being able to access the profile (Access 
138Denied) and create multiple copies of it on disk (DOMAIN.user.001,
139DOMAIN.user.002, and so on). See the <tt class="filename">smb.conf</tt> man page
140for more details on this option. Also note that the 
141<a class="indexterm" name="id2620570"></a>nt acl support parameter was formally a global parameter in
142releases prior to Samba 2.2.2.
143</p><p> 
144<a href="Other-Clients.html#minimalprofile" title="Example�40.1.�Minimal profile share">Following example</a> provides a minimal profile share.
145</p><div class="example"><a name="minimalprofile"></a><p class="title"><b>Example�40.1.�Minimal profile share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[profile]</tt></i></td></tr><tr><td><a class="indexterm" name="id2620615"></a><i class="parameter"><tt>
146					
147				path = /export/profile</tt></i></td></tr><tr><td><a class="indexterm" name="id2620630"></a><i class="parameter"><tt>
148					
149				create mask = 0600</tt></i></td></tr><tr><td><a class="indexterm" name="id2620646"></a><i class="parameter"><tt>
150					
151				directory mask = 0700</tt></i></td></tr><tr><td><a class="indexterm" name="id2620661"></a><i class="parameter"><tt>
152					
153				nt acl support = no</tt></i></td></tr><tr><td><a class="indexterm" name="id2620677"></a><i class="parameter"><tt>
154					
155				read only = no</tt></i></td></tr></table></div><p>
156The reason for this bug is that the Windows 200x SP2 client copies
157the security descriptor for the profile that contains
158the Samba server's SID, and not the domain SID. The client
159compares the SID for SAMBA\user and realizes it is
160different from the one assigned to DOMAIN\user. Hence, the reason
161for the <span class="errorname">access denied</span> message.
162</p><p>
163By disabling the <a class="indexterm" name="id2620707"></a>nt acl support parameter, Samba will send
164the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client
165to set a default ACL for the profile. This default ACL includes:
166</p><p><span class="emphasis"><em>DOMAIN\user 	&#8220;<span class="quote"><span class="emphasis"><em>Full Control</em></span></span>&#8221;</em></span>&gt;</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This bug does not occur when using Winbind to
167create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620735"></a>Windows NT 3.1</h2></div></div></div><p>If you have problems communicating across routers with Windows 
168NT 3.1 workstations, read <a href="http://support.microsoft.com/default.aspx?scid=kb;Q103765" target="_top">this Microsoft Knowledge Base article.</a>
169
170</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Portability.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="Appendix.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="speed.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�39.�Portability�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�41.�Samba Performance Tuning</td></tr></table></div></body></html>
171