1<?xml version="1.0" encoding="iso-8859-1"?> 2<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc"> 3<chapter id="Other-Clients"> 4<chapterinfo> 5 &author.jelmer; 6 &author.jht; 7 &author.danshearer; 8 <author>&person.jmcd;<contrib>OS/2</contrib></author> 9 <pubdate>5 Mar 2001</pubdate> 10</chapterinfo> 11 12<title>Samba and Other CIFS Clients</title> 13 14<para>This chapter contains client-specific information.</para> 15 16<sect1> 17<title>Macintosh Clients</title> 18 19<para> 20<indexterm><primary>DAVE</primary></indexterm> 21Yes. <ulink url="http://www.thursby.com/">Thursby</ulink> has a CIFS client/server called <ulink 22url="http://www.thursby.com/products/dave.html">DAVE</ulink>. They test it against Windows 95, Windows 23NT/200x/XP, and Samba for compatibility issues. At the time of this writing, DAVE was at version 5.1. Please 24refer to Thursby's Web site for more information regarding this product. 25</para> 26 27<para> 28<indexterm><primary>Netatalk</primary></indexterm> 29<indexterm><primary>CAP</primary></indexterm> 30Alternatives include two free implementations of AppleTalk for several kinds of UNIX machines and several more 31commercial ones. These products allow you to run file services and print services natively to Macintosh 32users, with no additional support required on the Macintosh. The two free implementations are <ulink 33url="http://www.umich.edu/~rsug/netatalk/">Netatalk</ulink> and <ulink 34url="http://www.cs.mu.oz.au/appletalk/atalk.html">CAP</ulink>. What Samba offers MS Windows users, these 35packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems), see 36<ulink noescape="1" url="http://www.eats.com/linux_mac_win.html">http://www.eats.com/linux_mac_win.html.</ulink> 37</para> 38 39<para>Newer versions of the Macintosh (Mac OS X) include Samba.</para> 40 41</sect1> 42 43<sect1> 44<title>OS2 Client</title> 45 46 <sect2> 47 <title>Configuring OS/2 Warp Connect or OS/2 Warp 4</title> 48 49 <para>Basically, you need three components:</para> 50 51 <itemizedlist> 52 <listitem><para>The File and Print Client (IBM peer)</para></listitem> 53 <listitem><para>TCP/IP (Internet support) </para></listitem> 54 <listitem><para>The <quote>NetBIOS over TCP/IP</quote> driver (TCPBEUI)</para></listitem> 55 </itemizedlist> 56 57 <para>Installing the first two together with the base operating 58 system on a blank system is explained in the Warp manual. If Warp 59 has already been installed, but you now want to install the 60 networking support, use the <quote>Selective Install for Networking</quote> 61 object in the <quote>System Setup</quote> folder.</para> 62 63 <para>Adding the <quote>NetBIOS over TCP/IP</quote> driver is not described 64 in the manual and just barely in the online documentation. Start 65 <command>MPTS.EXE</command>, click on <guiicon>OK</guiicon>, click on <guimenu>Configure LAPS</guimenu>, and click 66 on <guimenu>IBM OS/2 NETBIOS OVER TCP/IP</guimenu> in <guilabel>Protocols</guilabel>. This line 67 is then moved to <guilabel>Current Configuration</guilabel>. Select that line, 68 click on <guimenuitem>Change number</guimenuitem>, and increase it from 0 to 1. Save this 69 configuration.</para> 70 71 <para>If the Samba server is not on your local subnet, you 72 can optionally add IP names and addresses of these servers 73 to the <guimenu>Names List</guimenu> or specify a WINS server (NetBIOS 74 Nameserver in IBM and RFC terminology). For Warp Connect, you 75 may need to download an update for <constant>IBM Peer</constant> to bring it on 76 the same level as Warp 4. See the IBM OS/2 Warp Web page</para> 77 </sect2> 78 79 <sect2> 80 <title>Configuring Other Versions of OS/2</title> 81 82 <para>This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.</para> 83 84 <para>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is 85 available from 86 <ulink noescape="1" url="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"> 87 ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</ulink>. In a nutshell, edit 88 the file <filename>\OS2VER</filename> in the root directory of the OS/2 boot partition and add the lines:</para> 89 90 <para><programlisting> 91 20=setup.exe 92 20=netwksta.sys 93 20=netvdd.sys 94 </programlisting></para> 95 96 <para>before you install the client. Also, do not use the included NE2000 driver because it is buggy. 97 Try the NE2000 or NS2000 driver from <ulink noescape="1" url="ftp://ftp.cdrom.com/pub/os2/network/ndis/"> 98 ftp://ftp.cdrom.com/pub/os2/network/ndis/</ulink> instead. 99 </para> 100 </sect2> 101 102 <sect2> 103 <title>Printer Driver Download for OS/2 Clients</title> 104 105 <para>Create a share called <smbconfsection name="[PRINTDRV]"/> that is 106 world-readable. Copy your OS/2 driver files there. The <filename>.EA_</filename> 107 files must still be separate, so you will need to use the original install files 108 and not copy an installed driver from an OS/2 system.</para> 109 110 <para>Install the NT driver first for that printer. Then, add to your &smb.conf; a parameter, 111 <smbconfoption name="os2 driver map"><replaceable>filename</replaceable></smbconfoption>. 112 Next, in the file specified by <replaceable>filename</replaceable>, map the 113 name of the NT driver name to the OS/2 driver name as follows:</para> 114 115 <para><parameter><replaceable>nt driver name</replaceable> = <replaceable>os2 driver name</replaceable>.<replaceable>device name</replaceable></parameter>, e.g.,</para> 116 117 <para><parameter> 118 HP LaserJet 5L = LASERJET.HP LaserJet 5L</parameter></para> 119 120 <para>You can have multiple drivers mapped in this file.</para> 121 122 <para>If you only specify the OS/2 driver name, and not the 123 device name, the first attempt to download the driver will 124 actually download the files, but the OS/2 client will tell 125 you the driver is not available. On the second attempt, it 126 will work. This is fixed simply by adding the device name 127 to the mapping, after which it will work on the first attempt. 128 </para> 129 </sect2> 130</sect1> 131 132<sect1> 133<title>Windows for Workgroups</title> 134 135<sect2> 136<title>Latest TCP/IP Stack from Microsoft</title> 137 138<para>Use the latest TCP/IP stack from Microsoft if you use Windows 139for Workgroups. The early TCP/IP stacks had lots of bugs.</para> 140 141<para> 142Microsoft has released an incremental upgrade to its TCP/IP 32-bit VxD drivers. The latest release can be 143found at ftp.microsoft.com, located in <filename>/Softlib/MSLFILES/TCP32B.EXE</filename>. There is an 144update.txt file there that describes the problems that were fixed. New files include 145<filename>WINSOCK.DLL</filename>, <filename>TELNET.EXE</filename>, <filename>WSOCK.386</filename>, 146<filename>VNBT.386</filename>, <filename>WSTCP.386</filename>, <filename>TRACERT.EXE</filename>, 147<filename>NETSTAT.EXE</filename>, and <filename>NBTSTAT.EXE</filename>. 148</para> 149 150<para> 151More information about this patch is available in <ulink 152url="http://support.microsoft.com/kb/q99891/">Knowledge Base article 99891</ulink>. 153</para> 154 155</sect2> 156 157<sect2> 158<title>Delete .pwl Files After Password Change</title> 159 160<para> 161Windows for Workgroups does a lousy job with passwords. When you change passwords on either 162the UNIX box or the PC, the safest thing to do is delete the .pwl files in the Windows 163directory. The PC will complain about not finding the files, but will soon get over it, 164allowing you to enter the new password. 165</para> 166 167<para> 168If you do not do this, you may find that Windows for Workgroups remembers and uses the old 169password, even if you told it a new one. 170</para> 171 172<para> 173Often Windows for Workgroups will totally ignore a password you give it in a dialog box. 174</para> 175 176</sect2> 177 178<sect2> 179<title>Configuring Windows for Workgroups Password Handling</title> 180 181<para> 182<indexterm><primary>admincfg.exe</primary></indexterm> 183There is a program call <filename>admincfg.exe</filename> on the last disk (disk 8) of the WFW 3.11 disk set. 184To install it, type <userinput>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</userinput>. Then add an icon 185for it via the <application>Program Manager</application> <guimenu>New</guimenu> menu. This program allows 186you to control how WFW handles passwords, Disable Password Caching and so on, for use with <smbconfoption 187name="security">user</smbconfoption>. 188</para> 189 190</sect2> 191 192<sect2> 193<title>Password Case Sensitivity</title> 194 195<para>Windows for Workgroups uppercases the password before sending it to the server. 196UNIX passwords can be case-sensitive though. Check the &smb.conf; information on 197<smbconfoption name="password level"/> to specify what characters 198Samba should try to uppercase when checking.</para> 199 200</sect2> 201 202<sect2> 203<title>Use TCP/IP as Default Protocol</title> 204 205<para>To support print queue reporting, you may find 206that you have to use TCP/IP as the default protocol under 207Windows for Workgroups. For some reason, if you leave NetBEUI as the default, 208it may break the print queue reporting on some systems. 209It is presumably a Windows for Workgroups bug.</para> 210 211</sect2> 212 213<sect2 id="speedimpr"> 214<title>Speed Improvement</title> 215 216<para> 217Note that some people have found that setting <parameter>DefaultRcvWindow</parameter> in 218the <smbconfsection name="[MSTCP]"/> section of the 219<filename>SYSTEM.INI</filename> file under Windows for Workgroups to 3072 gives a 220big improvement. 221</para> 222 223<para> 224My own experience with DefaultRcvWindow is that I get a much better 225performance with a large value (16384 or larger). Other people have 226reported that anything over 3072 slows things down enormously. One 227person even reported a speed drop of a factor of 30 when he went from 2283072 to 8192. 229</para> 230</sect2> 231</sect1> 232 233<sect1> 234<title>Windows 95/98</title> 235 236<para> 237When using Windows 95 OEM SR2, the following updates are recommended where Samba 238is being used. Please note that the changes documented in 239<link linkend="speedimpr">Speed Improvement</link> will affect you once these 240updates have been installed. 241</para> 242 243<para> 244There are more updates than the ones mentioned here. Refer to the 245Microsoft Web site for all currently available updates to your specific version 246of Windows 95. 247</para> 248 249<simplelist> 250<member>Kernel Update: KRNLUPD.EXE</member> 251<member>Ping Fix: PINGUPD.EXE</member> 252<member>RPC Update: RPCRTUPD.EXE</member> 253<member>TCP/IP Update: VIPUPD.EXE</member> 254<member>Redirector Update: VRDRUPD.EXE</member> 255</simplelist> 256 257<para> 258Also, if using <application>MS Outlook,</application> it is desirable to 259install the <command>OLEUPD.EXE</command> fix. This 260fix may stop your machine from hanging for an extended period when exiting 261Outlook, and you may notice a significant speedup when accessing network 262neighborhood services. 263</para> 264 265<sect2> 266<title>Speed Improvement</title> 267 268<para> 269Configure the Windows 95 TCP/IP registry settings to give better 270performance. I use a program called <command>MTUSPEED.exe</command> that I got off the 271Internet. There are various other utilities of this type freely available. 272</para> 273 274</sect2> 275 276</sect1> 277 278<sect1> 279<title>Windows 2000 Service Pack 2</title> 280 281<para> 282There are several annoyances with Windows 2000 SP2, one of which 283only appears when using a Samba server to host user profiles 284to Windows 2000 SP2 clients in a Windows domain. This assumes 285that Samba is a member of the domain, but the problem will 286most likely occur if it is not. 287</para> 288 289<para> 290In order to serve profiles successfully to Windows 2000 SP2 291clients (when not operating as a PDC), Samba must have 292<smbconfoption name="nt acl support">no</smbconfoption> 293added to the file share that houses the roaming profiles. 294If this is not done, then the Windows 2000 SP2 client will 295complain about not being able to access the profile (Access 296Denied) and create multiple copies of it on disk (DOMAIN.user.001, 297DOMAIN.user.002, and so on). See the &smb.conf; man page 298for more details on this option. Also note that the 299<smbconfoption name="nt acl support"/> parameter was formally a global parameter in 300releases prior to Samba 2.2.2. 301</para> 302 303<para> 304<link linkend="minimalprofile">Following example</link> provides a minimal profile share. 305</para> 306 307<example id="minimalprofile"> 308<title>Minimal Profile Share</title> 309<smbconfblock> 310<smbconfsection name="[profile]"/> 311<smbconfoption name="path">/export/profile</smbconfoption> 312<smbconfoption name="create mask">0600</smbconfoption> 313<smbconfoption name="directory mask">0700</smbconfoption> 314<smbconfoption name="nt acl support">no</smbconfoption> 315<smbconfoption name="read only">no</smbconfoption> 316</smbconfblock> 317</example> 318 319<para> 320The reason for this bug is that the Windows 200x SP2 client copies 321the security descriptor for the profile that contains 322the Samba server's SID, and not the domain SID. The client 323compares the SID for SAMBA\user and realizes it is 324different from the one assigned to DOMAIN\user; hence, 325<errorname>access denied</errorname> message. 326</para> 327 328<para> 329When the <smbconfoption name="nt acl support"/> parameter is disabled, Samba will send 330the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client 331to set a default ACL for the profile. This default ACL includes: 332</para> 333 334<para><emphasis>DOMAIN\user <quote>Full Control</quote></emphasis>></para> 335 336<note><para>This bug does not occur when using Winbind to 337create accounts on the Samba host for Domain users.</para></note> 338 339</sect1> 340 341<sect1> 342<title>Windows NT 3.1</title> 343 344<para>If you have problems communicating across routers with Windows 345NT 3.1 workstations, read <ulink url="http://support.microsoft.com/default.aspx?scid=kb;Q103765">this Microsoft Knowledge Base article:</ulink>. 346 347</para> 348 349</sect1> 350 351</chapter> 352