docs/docbook/projdoc/OS2-Client-HOWTO.sgml

   1 <chapter>
   2
   3
   4 <chapterinfo>
   5         <author>
   6                 <firstname>Jim</firstname><surname>McDonough</surname>
   7                 <affiliation>
   8                         <orgname>IBM</orgname>
   9                         <address>
  10                                 <email>jerry@samba.org</email>
  11                         </address>
  12                 </affiliation>
  13         </author>
  14
  15
  16         <pubdate>5 Mar 2001</pubdate>
  17 </chapterinfo>
  18
  19 <title>OS2 Client HOWTO</title>
  20
  21 <sect1>
  22         <title>FAQs</title>
  23
  24         <sect2>
  25                 <title>How can I configure OS/2 Warp Connect or
  26                 OS/2 Warp 4 as a client for Samba?</title>
  27
  28                 <para>A more complete answer to this question can be
  29                 found on <ulink url="http://carol.wins.uva.nl/~leeuw/samba/warp.html">
  30                 http://carol.wins.uva.nl/~leeuw/samba/warp.html</ulink>.</para>
  31
  32                 <para>Basically, you need three components:</para>
  33
  34                 <itemizedlist>
  35                         <listitem><para>The File and Print Client ('IBM Peer')
  36                         </para></listitem>
  37                         <listitem><para>TCP/IP ('Internet support')
  38                         </para></listitem>
  39                         <listitem><para>The "NetBIOS over TCP/IP" driver ('TCPBEUI')
  40                         </para></listitem>
  41                 </itemizedlist>
  42
  43                 <para>Installing the first two together with the base operating
  44                 system on a blank system is explained in the Warp manual. If Warp
  45                 has already been installed, but you now want to install the
  46                 networking support, use the "Selective Install for Networking"
  47                 object in the "System Setup" folder.</para>
  48
  49                 <para>Adding the "NetBIOS over TCP/IP" driver is not described
  50                 in the manual and just barely in the online documentation. Start
  51                 MPTS.EXE, click on OK, click on "Configure LAPS" and click
  52                 on "IBM OS/2 NETBIOS OVER TCP/IP" in  'Protocols'.  This line
  53                 is then moved to 'Current Configuration'. Select that line,
  54                 click on "Change number" and increase it from 0 to 1. Save this
  55                 configuration.</para>
  56
  57                 <para>If the Samba server(s) is not on your local subnet, you
  58                 can optionally add IP names and addresses of these servers
  59                 to the "Names List", or specify a  WINS server ('NetBIOS
  60                 Nameserver' in IBM and RFC terminology). For Warp Connect you
  61                 may need to download an update for 'IBM Peer' to bring it on
  62                 the same level as Warp 4. See the webpage mentioned above.</para>
  63         </sect2>
  64
  65         <sect2>
  66                 <title>How can I configure OS/2 Warp 3 (not Connect),
  67                 OS/2 1.2, 1.3 or 2.x for Samba?</title>
  68
  69                 <para>You can use the free Microsoft LAN Manager 2.2c Client
  70                 for OS/2 from
  71                 <ulink url="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/">
  72                 ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</ulink>.
  73         See <ulink url="http://carol.wins.uva.nl/~leeuw/lanman.html">
  74                 http://carol.wins.uva.nl/~leeuw/lanman.html</ulink> for
  75                 more information on how to install and use this client. In
  76                 a nutshell, edit the file \OS2VER in the root directory of
  77                 the OS/2 boot partition and add the lines:</para>
  78
  79                 <para><programlisting>
  80                 20=setup.exe
  81                 20=netwksta.sys
  82                 20=netvdd.sys
  83                 </programlisting></para>
  84
  85                 <para>before you install the client. Also, don't use the
  86                 included NE2000 driver because it is buggy. Try the NE2000
  87                 or NS2000 driver from
  88                 <ulink url="ftp://ftp.cdrom.com/pub/os2/network/ndis/">
  89                 ftp://ftp.cdrom.com/pub/os2/network/ndis/</ulink> instead.
  90                 </para>
  91         </sect2>
  92
  93         <sect2>
  94                 <title>Are there any other issues when OS/2 (any version)
  95                 is used as a client?</title>
  96
  97                 <para>When you do a NET VIEW or use the "File and Print
  98                 Client Resource Browser", no Samba servers show up. This can
  99                 be fixed by a patch from <ulink
 100                 url="http://carol.wins.uva.nl/~leeuw/samba/fix.html">
 101                 http://carol.wins.uva.nl/~leeuw/samba/fix.html</ulink>.
 102                 The patch will be included in a later version of Samba. It also
 103                 fixes a couple of other problems, such as preserving long
 104                 filenames when objects are dragged from the Workplace Shell
 105                 to the Samba server. </para>
 106         </sect2>
 107
 108         <sect2>
 109                 <title>How do I get printer driver download working
 110                 for OS/2 clients?</title>
 111
 112                 <para>First, create a share called [PRINTDRV] that is
 113                 world-readable.  Copy your OS/2 driver files there.  Note
 114                 that the .EA_ files must still be separate, so you will need
 115                 to use the original install files, and not copy an installed
 116                 driver from an OS/2 system.</para>
 117
 118                 <para>Install the NT driver first for that printer.  Then,
 119                 add to your smb.conf a paramater, "os2 driver map =
 120                 <replaceable>filename</replaceable>".  Then, in the file
 121                 specified by <replaceable>filename</replaceable>, map the
 122                 name of the NT driver name to the OS/2 driver name as
 123                 follows:</para>
 124
 125                 <para>&lt;nt driver name&gt; = &lt;os2 driver
 126                 name&gt;.&lt;device name&gt;, e.g.:
 127                 HP LaserJet 5L = LASERJET.HP LaserJet 5L</para>
 128
 129                 <para>You can have multiple drivers mapped in this file.</para>
 130
 131                 <para>If you only specify the OS/2 driver name, and not the
 132                 device name, the first attempt to download the driver will
 133                 actually download the files, but the OS/2 client will tell
 134                 you the driver is not available.  On the second attempt, it
 135                 will work.  This is fixed simply by adding the device name
 136                  to the mapping, after which it will work on the first attempt.
 137                 </para>
 138         </sect2>
 139 </sect1>
 140
 141 </chapter>
 142