diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/Other-Clients.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/Other-Clients.html | 151 |
1 files changed, 151 insertions, 0 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/Other-Clients.html b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html new file mode 100644 index 0000000000..3e3d50367c --- /dev/null +++ b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html @@ -0,0 +1,151 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 43. Samba and Other CIFS Clients</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Portability.html" title="Chapter 42. Portability"><link rel="next" href="speed.html" title="Chapter 44. 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 43. 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. Reference Section</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 43. 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><code class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></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><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></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><code class="email"><<a href="mailto:dan@samba.org">dan@samba.org</a>></code></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><code class="email"><<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>></code></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#id444113">Macintosh Clients</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id444188">OS2 Client</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id444194">Configuring OS/2 Warp Connect or OS/2 Warp 4</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444304">Configuring Other Versions of OS/2</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444354">Printer Driver Download for OS/2 Clients</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id444434">Windows for Workgroups</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id444440">Latest TCP/IP Stack from Microsoft</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444518">Delete .pwl Files After Password Change</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444539">Configuring Windows for Workgroups Password Handling</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444589">Password Case Sensitivity</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#id444614">Use TCP/IP as Default Protocol</a></span></dt><dt><span class="sect2"><a href="Other-Clients.html#speedimpr">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id444665">Windows 95/98</a></span></dt><dd><dl><dt><span class="sect2"><a href="Other-Clients.html#id444728">Speed Improvement</a></span></dt></dl></dd><dt><span class="sect1"><a href="Other-Clients.html#id444747">Windows 2000 Service Pack 2</a></span></dt><dt><span class="sect1"><a href="Other-Clients.html#id444921">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="id444113"></a>Macintosh Clients</h2></div></div></div><p> +<a class="indexterm" name="id444121"></a> +Yes. <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>. They test it against Windows 95, Windows +NT/200x/XP, and Samba for compatibility issues. At the time of this writing, DAVE was at version 5.1. Please +refer to Thursby's Web site for more information regarding this product. +</p><p> +<a class="indexterm" name="id444145"></a> +<a class="indexterm" name="id444152"></a> +Alternatives include two free implementations of AppleTalk for several kinds of UNIX machines and several more +commercial ones. These products allow you to run file services and print services natively to Macintosh +users, with no additional support required on the Macintosh. The two free implementations are <a href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk</a> and <a href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP</a>. What Samba offers MS Windows users, these +packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems), see +<a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html.</a> +</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="id444188"></a>OS2 Client</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444194"></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 “<span class="quote">NetBIOS over TCP/IP</span>” driver (TCPBEUI)</p></li></ul></div><p>Installing the first two together with the base operating + system on a blank system is explained in the Warp manual. If Warp + has already been installed, but you now want to install the + networking support, use the “<span class="quote">Selective Install for Networking</span>” + object in the “<span class="quote">System Setup</span>” folder.</p><p>Adding the “<span class="quote">NetBIOS over TCP/IP</span>” driver is not described + in the manual and just barely in the online documentation. Start + <code class="literal">MPTS.EXE</code>, click on <span class="guiicon">OK</span>, click on <span class="guimenu">Configure LAPS</span>, and click + on <span class="guimenu">IBM OS/2 NETBIOS OVER TCP/IP</span> in <span class="guilabel">Protocols</span>. This line + is then moved to <span class="guilabel">Current Configuration</span>. Select that line, + click on <span class="guimenuitem">Change number</span>, and increase it from 0 to 1. Save this + configuration.</p><p>If the Samba server is not on your local subnet, you + can optionally add IP names and addresses of these servers + to the <span class="guimenu">Names List</span> or specify a WINS server (NetBIOS + Nameserver in IBM and RFC terminology). For Warp Connect, you + may need to download an update for <code class="constant">IBM Peer</code> to bring it on + the same level as Warp 4. See the IBM OS/2 Warp Web page</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444304"></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 + available from + <a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top"> + ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>. In a nutshell, edit + the file <code class="filename">\OS2VER</code> in the root directory of the OS/2 boot partition and add the lines:</p><pre class="programlisting"> + 20=setup.exe + 20=netwksta.sys + 20=netvdd.sys + </pre><p>before you install the client. Also, do not use the included NE2000 driver because it is buggy. + Try the NE2000 or NS2000 driver from <a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top"> + ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444354"></a>Printer Driver Download for OS/2 Clients</h3></div></div></div><p>Create a share called <em class="parameter"><code>[PRINTDRV]</code></em> that is + world-readable. Copy your OS/2 driver files there. The <code class="filename">.EA_</code> + files must still be separate, so you will need to use the original install files + 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 <code class="filename">smb.conf</code> a parameter, + <a class="indexterm" name="id444386"></a>os2 driver map. + Next, in the file specified by <em class="replaceable"><code>filename</code></em>, map the + name of the NT driver name to the OS/2 driver name as follows:</p><p><em class="parameter"><code><em class="replaceable"><code>nt driver name</code></em> = <em class="replaceable"><code>os2 driver name</code></em>.<em class="replaceable"><code>device name</code></em></code></em>, e.g.,</p><p><em class="parameter"><code> + HP LaserJet 5L = LASERJET.HP LaserJet 5L</code></em></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 + device name, the first attempt to download the driver will + actually download the files, but the OS/2 client will tell + you the driver is not available. On the second attempt, it + will work. This is fixed simply by adding the device name + to the mapping, after which it will work on the first attempt. + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id444434"></a>Windows for Workgroups</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444440"></a>Latest TCP/IP Stack from Microsoft</h3></div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows +for Workgroups. The early TCP/IP stacks had lots of bugs.</p><p> +Microsoft has released an incremental upgrade to its TCP/IP 32-bit VxD drivers. The latest release can be +found at ftp.microsoft.com, located in <code class="filename">/Softlib/MSLFILES/TCP32B.EXE</code>. There is an +update.txt file there that describes the problems that were fixed. New files include +<code class="filename">WINSOCK.DLL</code>, <code class="filename">TELNET.EXE</code>, <code class="filename">WSOCK.386</code>, +<code class="filename">VNBT.386</code>, <code class="filename">WSTCP.386</code>, <code class="filename">TRACERT.EXE</code>, +<code class="filename">NETSTAT.EXE</code>, and <code class="filename">NBTSTAT.EXE</code>. +</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="id444518"></a>Delete .pwl Files After Password Change</h3></div></div></div><p> +Windows for Workgroups does a lousy job with passwords. When you change passwords on either +the UNIX box or the PC, the safest thing to do is 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. +</p><p> +If you do not do this, you may find that Windows for Workgroups remembers and uses the old +password, even if you told it a new one. +</p><p> +Often Windows for Workgroups will totally ignore a password you give it in a dialog box. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444539"></a>Configuring Windows for Workgroups Password Handling</h3></div></div></div><p> +<a class="indexterm" name="id444547"></a> +There is a program call <code class="filename">admincfg.exe</code> on the last disk (disk 8) of the WFW 3.11 disk set. +To install it, type <strong class="userinput"><code>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</code></strong>. Then add an icon +for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> menu. This program allows +you to control how WFW handles passwords, Disable Password Caching and so on, for use with <a class="indexterm" name="id444580"></a>security = user. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444589"></a>Password Case Sensitivity</h3></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 <code class="filename">smb.conf</code> information on +<a class="indexterm" name="id444604"></a>password level 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="id444614"></a>Use TCP/IP as Default Protocol</h3></div></div></div><p>To support print queue reporting, you may find +that you have to use TCP/IP as the default protocol under +Windows for Workgroups. For some reason, if you leave NetBEUI as the default, +it may break the print queue reporting on some systems. +It is presumably a Windows for Workgroups bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="speedimpr"></a>Speed Improvement</h3></div></div></div><p> +Note that some people have found that setting <em class="parameter"><code>DefaultRcvWindow</code></em> in +the <em class="parameter"><code>[MSTCP]</code></em> section of the +<code class="filename">SYSTEM.INI</code> file under Windows for Workgroups to 3072 gives a +big improvement. +</p><p> +My own experience with DefaultRcvWindow is that I get a much better +performance with a large value (16384 or larger). Other people have +reported that anything over 3072 slows things down enormously. One +person even reported a speed drop of a factor of 30 when he went from +3072 to 8192. +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id444665"></a>Windows 95/98</h2></div></div></div><p> +When using Windows 95 OEM SR2, the following updates are recommended where Samba +is being used. Please note that the changes documented in +<a href="Other-Clients.html#speedimpr" title="Speed Improvement">Speed Improvement</a> will affect you once these +updates have been installed. +</p><p> +There are more updates than the ones mentioned here. Refer to the +Microsoft Web site for all currently available updates to your specific version +of Windows 95. +</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> +Also, if using <span class="application">MS Outlook,</span> it is desirable to +install the <code class="literal">OLEUPD.EXE</code> fix. This +fix may stop your machine from hanging for an extended period when exiting +Outlook, and you may notice a significant speedup when accessing network +neighborhood services. +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id444728"></a>Speed Improvement</h3></div></div></div><p> +Configure the Windows 95 TCP/IP registry settings to give better +performance. I use a program called <code class="literal">MTUSPEED.exe</code> that I got off the +Internet. There are various other utilities of this type freely available. +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id444747"></a>Windows 2000 Service Pack 2</h2></div></div></div><p> +There are several annoyances with Windows 2000 SP2, one of which +only appears when using a Samba server to host user profiles +to Windows 2000 SP2 clients in a Windows domain. This assumes +that Samba is a member of the domain, but the problem will +most likely occur if it is not. +</p><p> +In order to serve profiles successfully to Windows 2000 SP2 +clients (when not operating as a PDC), Samba must have +<a class="indexterm" name="id444761"></a>nt acl support = no +added to the file share that houses the roaming profiles. +If this is not done, then the Windows 2000 SP2 client will +complain about not being able to access the profile (Access +Denied) and create multiple copies of it on disk (DOMAIN.user.001, +DOMAIN.user.002, and so on). See the <code class="filename">smb.conf</code> man page +for more details on this option. Also note that the +<a class="indexterm" name="id444777"></a>nt acl support parameter was formally a global parameter in +releases prior to Samba 2.2.2. +</p><p> +<a href="Other-Clients.html#minimalprofile" title="Example 43.1. Minimal Profile Share">Following example</a> provides a minimal profile share. +</p><div class="example"><a name="minimalprofile"></a><p class="title"><b>Example 43.1. Minimal Profile Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[profile]</code></em></td></tr><tr><td><a class="indexterm" name="id444821"></a><em class="parameter"><code>path = /export/profile</code></em></td></tr><tr><td><a class="indexterm" name="id444834"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id444846"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr><tr><td><a class="indexterm" name="id444859"></a><em class="parameter"><code>nt acl support = no</code></em></td></tr><tr><td><a class="indexterm" name="id444871"></a><em class="parameter"><code>read only = no</code></em></td></tr></table></div></div><br class="example-break"><p> +The reason for this bug is that the Windows 200x SP2 client copies +the security descriptor for the profile that contains +the Samba server's SID, and not the domain SID. The client +compares the SID for SAMBA\user and realizes it is +different from the one assigned to DOMAIN\user; hence, +<span class="errorname">access denied</span> message. +</p><p> +When the <a class="indexterm" name="id444897"></a>nt acl support parameter is disabled, Samba will send +the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client +to set a default ACL for the profile. This default ACL includes: +</p><p><span class="emphasis"><em>DOMAIN\user “<span class="quote">Full Control</span>”</em></span>></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 +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="id444921"></a>Windows NT 3.1</h2></div></div></div><p>If you have problems communicating across routers with Windows +NT 3.1 workstations, read <a href="http://support.microsoft.com/default.aspx?scid=kb;Q103765" target="_top">this Microsoft Knowledge Base article:</a>. + +</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 42. Portability </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 44. Samba Performance Tuning</td></tr></table></div></body></html> |