1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
4 <!ENTITY % global_entities SYSTEM '../entities/global.entities'>
7 <chapter id="Other-Clients">
12 <author>&person.jmcd;<contrib>OS/2</contrib></author>
13 <pubdate>5 Mar 2001</pubdate>
16 <title>Samba and Other CIFS Clients</title>
18 <para>This chapter contains client-specific information.</para>
21 <title>Macintosh Clients</title>
24 Yes. <ulink url="http://www.thursby.com/">Thursby</ulink> has a CIFS Client/Server called <ulink url="http://www.thursby.com/products/dave.html">DAVE.</ulink>
25 They test it against Windows 95, Windows NT /200x/XP and Samba for
26 compatibility issues. At the time of this writing, DAVE was at version
27 4.1. Please refer to Thursby's Web site for more information regarding this
32 Alternatives &smbmdash; There are two free implementations of AppleTalk for
33 several kinds of UNIX machines and several more commercial ones.
34 These products allow you to run file services and print services
35 natively to Macintosh users, with no additional support required on
36 the Macintosh. The two free implementations are
37 <ulink url="http://www.umich.edu/~rsug/netatalk/">Netatalk,</ulink> and
38 <ulink url="http://www.cs.mu.oz.au/appletalk/atalk.html">CAP.</ulink>
39 What Samba offers MS Windows users, these packages offer to Macs.
40 For more info on these packages, Samba, and Linux (and other UNIX-based systems), see
41 <ulink noescape="1" url="http://www.eats.com/linux_mac_win.html">http://www.eats.com/linux_mac_win.html.</ulink>
44 <para>Newer versions of the Macintosh (Mac OS X) include Samba.</para>
49 <title>OS2 Client</title>
52 <title>Configuring OS/2 Warp Connect or OS/2 Warp 4</title>
54 <para>Basically, you need three components:</para>
57 <listitem>The File and Print Client (IBM Peer)</listitem>
58 <listitem>TCP/IP (Internet support) </listitem>
59 <listitem>The <quote>NetBIOS over TCP/IP</quote> driver (TCPBEUI)</listitem>
62 <para>Installing the first two together with the base operating
63 system on a blank system is explained in the Warp manual. If Warp
64 has already been installed, but you now want to install the
65 networking support, use the <quote>Selective Install for Networking</quote>
66 object in the <quote>System Setup</quote> folder.</para>
68 <para>Adding the <quote>NetBIOS over TCP/IP</quote> driver is not described
69 in the manual and just barely in the online documentation. Start
70 <command>MPTS.EXE</command>, click on <guiicon>OK</guiicon>, click on <guimenu>Configure LAPS</guimenu> and click
71 on <guimenu>IBM OS/2 NETBIOS OVER TCP/IP</guimenu> in <guilabel>Protocols</guilabel>. This line
72 is then moved to <guilabel>Current Configuration</guilabel>. Select that line,
73 click on <guimenuitem>Change number</guimenuitem> and increase it from 0 to 1. Save this
76 <para>If the Samba server is not on your local subnet, you
77 can optionally add IP names and addresses of these servers
78 to the <guimenu>Names List</guimenu>, or specify a WINS server (NetBIOS
79 Nameserver in IBM and RFC terminology). For Warp Connect, you
80 may need to download an update for <constant>IBM Peer</constant> to bring it on
81 the same level as Warp 4. See the Web page mentioned above.</para>
85 <title>Configuring Other Versions of OS/2</title>
87 <para>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</para>
89 <para>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is
91 <ulink noescape="1" url="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/">
92 ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</ulink>. In a nutshell, edit
93 the file <filename>\OS2VER</filename> in the root directory of the OS/2 boot partition and add the lines:</para>
95 <para><programlisting>
99 </programlisting></para>
101 <para>before you install the client. Also, do not use the included NE2000 driver because it is buggy.
102 Try the NE2000 or NS2000 driver from <ulink noescape="1" url="ftp://ftp.cdrom.com/pub/os2/network/ndis/">
103 ftp://ftp.cdrom.com/pub/os2/network/ndis/</ulink> instead.
108 <title>Printer Driver Download for OS/2 Clients</title>
110 <para>Create a share called <smbconfsection>[PRINTDRV]</smbconfsection> that is
111 world-readable. Copy your OS/2 driver files there. The <filename>.EA_</filename>
112 files must still be separate, so you will need to use the original install files
113 and not copy an installed driver from an OS/2 system.</para>
115 <para>Install the NT driver first for that printer. Then, add to your &smb.conf; a parameter,
116 <smbconfoption><name>os2 driver map</name><value><replaceable>filename</replaceable></value></smbconfoption>.
117 Next, in the file specified by <replaceable>filename</replaceable>, map the
118 name of the NT driver name to the OS/2 driver name as follows:</para>
120 <para><parameter><replaceable>nt driver name</replaceable> = <replaceable>os2 driver name</replaceable>.<replaceable>device name</replaceable></parameter>, e.g.</para>
123 HP LaserJet 5L = LASERJET.HP LaserJet 5L</parameter></para>
125 <para>You can have multiple drivers mapped in this file.</para>
127 <para>If you only specify the OS/2 driver name, and not the
128 device name, the first attempt to download the driver will
129 actually download the files, but the OS/2 client will tell
130 you the driver is not available. On the second attempt, it
131 will work. This is fixed simply by adding the device name
132 to the mapping, after which it will work on the first attempt.
138 <title>Windows for Workgroups</title>
141 <title>Latest TCP/IP Stack from Microsoft</title>
143 <para>Use the latest TCP/IP stack from Microsoft if you use Windows
144 for Workgroups. The early TCP/IP stacks had lots of bugs.</para>
147 Microsoft has released an incremental upgrade to their TCP/IP 32-bit
148 VxD drivers. The latest release can be found on their ftp site at
149 ftp.microsoft.com, located in <filename>/peropsys/windows/public/tcpip/wfwt32.exe</filename>.
150 There is an update.txt file there that describes the problems that were
151 fixed. New files include <filename>WINSOCK.DLL</filename>,
152 <filename>TELNET.EXE</filename>,
153 <filename>WSOCK.386</filename>,
154 <filename>VNBT.386</filename>,
155 <filename>WSTCP.386</filename>,
156 <filename>TRACERT.EXE</filename>,
157 <filename>NETSTAT.EXE</filename>, and
158 <filename>NBTSTAT.EXE</filename>.
164 <title>Delete .pwl Files After Password Change</title>
167 Windows for Workgroups does a lousy job with passwords. When you change passwords on either
168 the UNIX box or the PC, the safest thing to do is to delete the .pwl files in the Windows
169 directory. The PC will complain about not finding the files, but will soon get over it,
170 allowing you to enter the new password.
174 If you do not do this, you may find that Windows for Workgroups remembers and uses the old
175 password, even if you told it a new one.
179 Often Windows for Workgroups will totally ignore a password you give it in a dialog box.
185 <title>Configuring Windows for Workgroups Password Handling</title>
188 There is a program call <filename>admincfg.exe</filename>
189 on the last disk (disk 8) of the WFW 3.11 disk set. To install it,
190 type <userinput>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</userinput>.
191 Then add an icon for it via the <application>Program Manager</application> <guimenu>New</guimenu> Menu.
192 This program allows you to control how WFW handles passwords, i.e.,
193 Disable Password Caching and so on.
194 for use with <smbconfoption><name>security</name><value>user</value></smbconfoption>.
200 <title>Password Case Sensitivity</title>
202 <para>Windows for Workgroups uppercases the password before sending it to the server.
203 UNIX passwords can be case-sensitive though. Check the &smb.conf; information on
204 <smbconfoption><name>password level</name></smbconfoption> to specify what characters
205 Samba should try to uppercase when checking.</para>
210 <title>Use TCP/IP as Default Protocol</title>
212 <para>To support print queue reporting, you may find
213 that you have to use TCP/IP as the default protocol under
214 Windows for Workgroups. For some reason, if you leave NetBEUI as the default,
215 it may break the print queue reporting on some systems.
216 It is presumably a Windows for Workgroups bug.</para>
221 <title>Speed Improvement</title>
224 Note that some people have found that setting <parameter>DefaultRcvWindow</parameter> in
225 the <smbconfsection>[MSTCP]</smbconfsection> section of the
226 <filename>SYSTEM.INI</filename> file under Windows for Workgroups to 3072 gives a
231 My own experience with DefaultRcvWindow is that I get a much better
232 performance with a large value (16384 or larger). Other people have
233 reported that anything over 3072 slows things down enormously. One
234 person even reported a speed drop of a factor of 30 when he went from
241 <title>Windows 95/98</title>
244 When using Windows 95 OEM SR2, the following updates are recommended where Samba
245 is being used. Please note that the above change will effect you once these
246 updates have been installed.
250 There are more updates than the ones mentioned here. You are referred to the
251 Microsoft Web site for all currently available updates to your specific version
256 <member>Kernel Update: KRNLUPD.EXE</member>
257 <member>Ping Fix: PINGUPD.EXE</member>
258 <member>RPC Update: RPCRTUPD.EXE</member>
259 <member>TCP/IP Update: VIPUPD.EXE</member>
260 <member>Redirector Update: VRDRUPD.EXE</member>
264 Also, if using <application>MS Outlook,</application> it is desirable to
265 install the <command>OLEUPD.EXE</command> fix. This
266 fix may stop your machine from hanging for an extended period when exiting
267 Outlook and you may notice a significant speedup when accessing network
268 neighborhood services.
272 <title>Speed Improvement</title>
275 Configure the Windows 95 TCP/IP registry settings to give better
276 performance. I use a program called <command>MTUSPEED.exe</command> that I got off the
277 Internet. There are various other utilities of this type freely available.
285 <title>Windows 2000 Service Pack 2</title>
288 There are several annoyances with Windows 2000 SP2. One of which
289 only appears when using a Samba server to host user profiles
290 to Windows 2000 SP2 clients in a Windows domain. This assumes
291 that Samba is a member of the domain, but the problem will
292 most likely occur if it is not.
296 In order to serve profiles successfully to Windows 2000 SP2
297 clients (when not operating as a PDC), Samba must have
298 <smbconfoption><name>nt acl support</name><value>no</value></smbconfoption>
299 added to the file share which houses the roaming profiles.
300 If this is not done, then the Windows 2000 SP2 client will
301 complain about not being able to access the profile (Access
302 Denied) and create multiple copies of it on disk (DOMAIN.user.001,
303 DOMAIN.user.002, and so on). See the &smb.conf; man page
304 for more details on this option. Also note that the
305 <smbconfoption><name>nt acl support</name></smbconfoption> parameter was formally a global parameter in
306 releases prior to Samba 2.2.2.
310 <link linkend="minimalprofile">Following example</link> provides a minimal profile share.
313 <para><smbconfexample id="minimalprofile">
314 <title>Minimal profile share</title>
315 <smbconfsection>[profile]</smbconfsection>
316 <smbconfoption><name>path</name><value>/export/profile</value></smbconfoption>
317 <smbconfoption><name>create mask</name><value>0600</value></smbconfoption>
318 <smbconfoption><name>directory mask</name><value>0700</value></smbconfoption>
319 <smbconfoption><name>nt acl support</name><value>no</value></smbconfoption>
320 <smbconfoption><name>read only</name><value>no</value></smbconfoption>
321 </smbconfexample></para>
324 The reason for this bug is that the Windows 200x SP2 client copies
325 the security descriptor for the profile that contains
326 the Samba server's SID, and not the domain SID. The client
327 compares the SID for SAMBA\user and realizes it is
328 different from the one assigned to DOMAIN\user. Hence, the reason
329 for the <errorname>access denied</errorname> message.
333 By disabling the <smbconfoption><name>nt acl support</name></smbconfoption> parameter, Samba will send
334 the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client
335 to set a default ACL for the profile. This default ACL includes:
338 <para><emphasis>DOMAIN\user <quote>Full Control</quote></emphasis>></para>
340 <note><para>This bug does not occur when using Winbind to
341 create accounts on the Samba host for Domain users.</para></note>
346 <title>Windows NT 3.1</title>
348 <para>If you have problems communicating across routers with Windows
349 NT 3.1 workstations, read <ulink url="http://support.microsoft.com/default.aspx?scid=kb;Q103765">this Microsoft Knowledge Base article.</ulink>