docs/htmldocs/Other-Clients.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 38. Samba and other CIFS clients</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="Part VI. Appendixes"><link rel="previous" href="Portability.html" title="Chapter 37. Portability"><link rel="next" href="speed.html" title="Chapter 39. 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 38. 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 38. Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><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><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><p class="pubdate">5 Mar 2001</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="Other-Clients.html#id3015663">Macintosh clients?</a></dt><dt><a href="Other-Clients.html#id3017016">OS2 Client</a></dt><dd><dl><dt><a href="Other-Clients.html#id3017023">How can I configure OS/2 Warp Connect or
   2                 OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="Other-Clients.html#id3017102">How can I configure OS/2 Warp 3 (not Connect),
   3                 OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="Other-Clients.html#id3017164">How do I get printer driver download working
   4                 for OS/2 clients?</a></dt></dl></dd><dt><a href="Other-Clients.html#id3017260">Windows for Workgroups</a></dt><dd><dl><dt><a href="Other-Clients.html#id3017268">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="Other-Clients.html#id3017357">Delete .pwl files after password change</a></dt><dt><a href="Other-Clients.html#id3017388">Configure WfW password handling</a></dt><dt><a href="Other-Clients.html#id3017433">Case handling of passwords</a></dt><dt><a href="Other-Clients.html#id3017464">Use TCP/IP as default protocol</a></dt><dt><a href="Other-Clients.html#id3017481">Speed improvement</a></dt></dl></dd><dt><a href="Other-Clients.html#id3017528">Windows '95/'98</a></dt><dd><dl><dt><a href="Other-Clients.html#id3017601">Speed improvement</a></dt></dl></dd><dt><a href="Other-Clients.html#id3017625">Windows 2000 Service Pack 2</a></dt><dt><a href="Other-Clients.html#id3017736">Windows NT 3.1</a></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="id3015663"></a>Macintosh clients?</h2></div></div><div></div></div><p>
   5 Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> now has a CIFS Client / Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a>
   6 </p><p>
   7 They test it against Windows 95, Windows NT and samba for
   8 compatibility issues.  At the time of writing, DAVE was at version
   9 1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
  10 the Thursby web site (the speed of finder copies has been greatly
  11 enhanced, and there are bug-fixes included).
  12 </p><p>
  13 Alternatives - There are two free implementations of AppleTalk for
  14 several kinds of UNIX machines, and several more commercial ones.
  15 These products allow you to run file services and print services
  16 natively to Macintosh users, with no additional support required on
  17 the Macintosh.  The two free implementations are
  18 <a href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk</a>, and
  19 <a href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP</a>.
  20 What Samba offers MS
  21 Windows users, these packages offer to Macs.  For more info on these
  22 packages, Samba, and Linux (and other UNIX-based systems) see
  23 <a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html</a>
  24 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3017016"></a>OS2 Client</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017023"></a>How can I configure OS/2 Warp Connect or
  25                 OS/2 Warp 4 as a client for Samba?</h3></div></div><div></div></div><p>A more complete answer to this question can be
  26                 found on <a href="http://carol.wins.uva.nl/~leeuw/samba/warp.html" target="_top">
  27                 http://carol.wins.uva.nl/~leeuw/samba/warp.html</a>.</p><p>Basically, you need three components:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>The File and Print Client ('IBM Peer')</td></tr><tr><td>TCP/IP ('Internet support') </td></tr><tr><td>The &quot;NetBIOS over TCP/IP&quot; driver ('TCPBEUI')</td></tr></table><p>Installing the first two together with the base operating
  28                 system on a blank system is explained in the Warp manual. If Warp
  29                 has already been installed, but you now want to install the
  30                 networking support, use the &quot;Selective Install for Networking&quot;
  31                 object in the &quot;System Setup&quot; folder.</p><p>Adding the &quot;NetBIOS over TCP/IP&quot; driver is not described
  32                 in the manual and just barely in the online documentation. Start
  33                 MPTS.EXE, click on OK, click on &quot;Configure LAPS&quot; and click
  34                 on &quot;IBM OS/2 NETBIOS OVER TCP/IP&quot; in  'Protocols'.  This line
  35                 is then moved to 'Current Configuration'. Select that line,
  36                 click on &quot;Change number&quot; and increase it from 0 to 1. Save this
  37                 configuration.</p><p>If the Samba server(s) is not on your local subnet, you
  38                 can optionally add IP names and addresses of these servers
  39                 to the &quot;Names List&quot;, or specify a  WINS server ('NetBIOS
  40                 Nameserver' in IBM and RFC terminology). For Warp Connect you
  41                 may need to download an update for 'IBM Peer' to bring it on
  42                 the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017102"></a>How can I configure OS/2 Warp 3 (not Connect),
  43                 OS/2 1.2, 1.3 or 2.x for Samba?</h3></div></div><div></div></div><p>You can use the free Microsoft LAN Manager 2.2c Client
  44                 for OS/2 from
  45                 <a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top">
  46                 ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>.
  47         See <a href="http://carol.wins.uva.nl/~leeuw/lanman.html" target="_top">
  48                 http://carol.wins.uva.nl/~leeuw/lanman.html</a> for
  49                 more information on how to install and use this client. In
  50                 a nutshell, edit the file \OS2VER in the root directory of
  51                 the OS/2 boot partition and add the lines:</p><pre class="programlisting">
  52                 20=setup.exe
  53                 20=netwksta.sys
  54                 20=netvdd.sys
  55                 </pre><p>before you install the client. Also, don't use the
  56                 included NE2000 driver because it is buggy. Try the NE2000
  57                 or NS2000 driver from
  58                 <a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top">
  59                 ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead.
  60                 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017164"></a>How do I get printer driver download working
  61                 for OS/2 clients?</h3></div></div><div></div></div><p>First, create a share called <i class="parameter"><tt>[PRINTDRV]</tt></i> that is
  62                 world-readable.  Copy your OS/2 driver files there.  Note
  63                 that the .EA_ files must still be separate, so you will need
  64                 to use the original install files, and not copy an installed
  65                 driver from an OS/2 system.</p><p>Install the NT driver first for that printer.  Then,
  66                 add to your <tt class="filename">smb.conf</tt> a parameter, <i class="parameter"><tt>os2 driver map =
  67                 <i class="replaceable"><tt>filename</tt></i></tt></i>.  Then, in the file
  68                 specified by <i class="replaceable"><tt>filename</tt></i>, map the
  69                 name of the NT driver name to the OS/2 driver name as
  70                 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>
  71                 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
  72                 device name, the first attempt to download the driver will
  73                 actually download the files, but the OS/2 client will tell
  74                 you the driver is not available.  On the second attempt, it
  75                 will work.  This is fixed simply by adding the device name
  76                  to the mapping, after which it will work on the first attempt.
  77                 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3017260"></a>Windows for Workgroups</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017268"></a>Use latest TCP/IP stack from Microsoft</h3></div></div><div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
  78 for Workgroups.
  79 </p><p>The early TCP/IP stacks had lots of bugs.</p><p>
  80 Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
  81 VxD drivers.  The latest release can be found on their ftp site at
  82 ftp.microsoft.com, located in <tt class="filename">/peropsys/windows/public/tcpip/wfwt32.exe</tt>.
  83 There is an update.txt file there that describes the problems that were
  84 fixed.  New files include <tt class="filename">WINSOCK.DLL</tt>,
  85 <tt class="filename">TELNET.EXE</tt>,
  86 <tt class="filename">WSOCK.386</tt>,
  87 <tt class="filename">VNBT.386</tt>,
  88 <tt class="filename">WSTCP.386</tt>,
  89 <tt class="filename">TRACERT.EXE</tt>,
  90 <tt class="filename">NETSTAT.EXE</tt>, and
  91 <tt class="filename">NBTSTAT.EXE</tt>.
  92 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017357"></a>Delete .pwl files after password change</h3></div></div><div></div></div><p>
  93 WfWg does a lousy job with passwords. I find that if I change my
  94 password on either the unix box or the PC the safest thing to do is to
  95 delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.
  96 </p><p>
  97 If you don't do this you may find that WfWg remembers and uses the old
  98 password, even if you told it a new one.
  99 </p><p>
 100 Often WfWg will totally ignore a password you give it in a dialog box.
 101 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017388"></a>Configure WfW password handling</h3></div></div><div></div></div><p>
 102 There is a program call admincfg.exe
 103 on the last disk (disk 8) of the WFW 3.11 disk set.  To install it
 104 type <b class="userinput"><tt>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</tt></b>.
 105 Then add an icon
 106 for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> Menu.
 107 This program allows you to control how WFW handles passwords.  ie disable Password Caching etc
 108 for use with <i class="parameter"><tt>security = user</tt></i>
 109 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017433"></a>Case handling of passwords</h3></div></div><div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> information on <i class="parameter"><tt>password level</tt></i> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017464"></a>Use TCP/IP as default protocol</h3></div></div><div></div></div><p>To support print queue reporting you may find
 110 that you have to use TCP/IP as the default protocol under
 111 WfWg. For some reason if you leave NetBEUI as the default
 112 it may break the print queue reporting on some systems.
 113 It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017481"></a>Speed improvement</h3></div></div><div></div></div><p>
 114 Note that some people have found that setting <i class="parameter"><tt>DefaultRcvWindow</tt></i> in
 115 the <i class="parameter"><tt>[MSTCP]</tt></i> section of the
 116 <tt class="filename">SYSTEM.INI</tt> file under WfWg to 3072 gives a
 117 big improvement. I don't know why.
 118 </p><p>
 119 My own experience with DefaultRcvWindow is that I get much better
 120 performance with a large value (16384 or larger). Other people have
 121 reported that anything over 3072 slows things down enormously. One
 122 person even reported a speed drop of a factor of 30 when he went from
 123 3072 to 8192. I don't know why.
 124 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3017528"></a>Windows '95/'98</h2></div></div><div></div></div><p>
 125 When using Windows 95 OEM SR2 the following updates are recommended where Samba
 126 is being used. Please NOTE that the above change will affect you once these
 127 updates  have been installed.
 128 </p><p>
 129 There are more updates than the ones mentioned here. You are referred to the
 130 Microsoft Web site for all currently available updates to your specific version
 131 of Windows 95.
 132 </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>
 133 Also, if using <span class="application">MS Outlook</span> it is desirable to
 134 install the <b class="command">OLEUPD.EXE</b> fix. This
 135 fix may stop your machine from hanging for an extended period when exiting
 136 Outlook and you may also notice a significant speedup when accessing network
 137 neighborhood services.
 138 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3017601"></a>Speed improvement</h3></div></div><div></div></div><p>
 139 Configure the win95 TCPIP registry settings to give better
 140 performance. I use a program called <b class="command">MTUSPEED.exe</b> which I got off the
 141 net. There are various other utilities of this type freely available.
 142 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3017625"></a>Windows 2000 Service Pack 2</h2></div></div><div></div></div><p>
 143 There are several annoyances with Windows 2000 SP2. One of which
 144 only appears when using a Samba server to host user profiles
 145 to Windows 2000 SP2 clients in a Windows domain.  This assumes
 146 that Samba is a member of the domain, but the problem will
 147 likely occur if it is not.
 148 </p><p>
 149 In order to serve profiles successfully to Windows 2000 SP2
 150 clients (when not operating as a PDC), Samba must have
 151 <i class="parameter"><tt>nt acl support = no</tt></i>
 152 added to the file share which houses the roaming profiles.
 153 If this is not done, then the Windows 2000 SP2 client will
 154 complain about not being able to access the profile (Access
 155 Denied) and create multiple copies of it on disk (DOMAIN.user.001,
 156 DOMAIN.user.002, etc...).  See the
 157 <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> man page
 158 for more details on this option.  Also note that the
 159 <i class="parameter"><tt>nt acl support</tt></i> parameter was formally a global parameter in
 160 releases prior to Samba 2.2.2.
 161 </p><p>
 162 The following is a minimal profile share:
 163 </p><pre class="programlisting">
 164         [profile]
 165                 path = /export/profile
 166                 create mask = 0600
 167                 directory mask = 0700
 168                 nt acl support = no
 169                 read only = no
 170 </pre><p>
 171 The reason for this bug is that the Win2k SP2 client copies
 172 the security descriptor for the profile which contains
 173 the Samba server's SID, and not the domain SID.  The client
 174 compares the SID for SAMBA\user and realizes it is
 175 different that the one assigned to DOMAIN\user.  Hence the reason
 176 for the <span class="errorname">access denied</span> message.
 177 </p><p>
 178 By disabling the <i class="parameter"><tt>nt acl support</tt></i> parameter, Samba will send
 179 the Win2k client a response to the QuerySecurityDescriptor
 180 trans2 call which causes the client to set a default ACL
 181 for the profile. This default ACL includes
 182 </p><p><span class="emphasis"><em>DOMAIN\user   &quot;Full Control&quot;</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
 183 create 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="id3017736"></a>Windows NT 3.1</h2></div></div><div></div></div><p>If you have problems communicating across routers with Windows
 184 NT 3.1 workstations, read <a href="http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;Q103765" target="_top">this Microsoft Knowledge Base article</a>.
 185
 186 </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="Appendixes.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 37. Portability </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 39. Samba Performance Tuning</td></tr></table></div></body></html>