docs/htmldocs/other-clients.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
   2 <HTML
   3 ><HEAD
   4 ><TITLE
   5 >Samba and other CIFS clients</TITLE
   6 ><META
   7 NAME="GENERATOR"
   8 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
   9 "><LINK
  10 REL="HOME"
  11 TITLE="SAMBA Project Documentation"
  12 HREF="samba-howto-collection.html"><LINK
  13 REL="UP"
  14 TITLE="Appendixes"
  15 HREF="appendixes.html"><LINK
  16 REL="PREVIOUS"
  17 TITLE="Portability"
  18 HREF="portability.html"><LINK
  19 REL="NEXT"
  20 TITLE="Reporting Bugs"
  21 HREF="bugreport.html"></HEAD
  22 ><BODY
  23 CLASS="CHAPTER"
  24 BGCOLOR="#FFFFFF"
  25 TEXT="#000000"
  26 LINK="#0000FF"
  27 VLINK="#840084"
  28 ALINK="#0000FF"
  29 ><DIV
  30 CLASS="NAVHEADER"
  31 ><TABLE
  32 SUMMARY="Header navigation table"
  33 WIDTH="100%"
  34 BORDER="0"
  35 CELLPADDING="0"
  36 CELLSPACING="0"
  37 ><TR
  38 ><TH
  39 COLSPAN="3"
  40 ALIGN="center"
  41 >SAMBA Project Documentation</TH
  42 ></TR
  43 ><TR
  44 ><TD
  45 WIDTH="10%"
  46 ALIGN="left"
  47 VALIGN="bottom"
  48 ><A
  49 HREF="portability.html"
  50 ACCESSKEY="P"
  51 >Prev</A
  52 ></TD
  53 ><TD
  54 WIDTH="80%"
  55 ALIGN="center"
  56 VALIGN="bottom"
  57 ></TD
  58 ><TD
  59 WIDTH="10%"
  60 ALIGN="right"
  61 VALIGN="bottom"
  62 ><A
  63 HREF="bugreport.html"
  64 ACCESSKEY="N"
  65 >Next</A
  66 ></TD
  67 ></TR
  68 ></TABLE
  69 ><HR
  70 ALIGN="LEFT"
  71 WIDTH="100%"></DIV
  72 ><DIV
  73 CLASS="CHAPTER"
  74 ><H1
  75 ><A
  76 NAME="OTHER-CLIENTS">Chapter 24. Samba and other CIFS clients</H1
  77 ><P
  78 >This chapter contains client-specific information.</P
  79 ><DIV
  80 CLASS="SECT1"
  81 ><H1
  82 CLASS="SECT1"
  83 ><A
  84 NAME="AEN3199">24.1. Macintosh clients?</H1
  85 ><P
  86 >Yes. <A
  87 HREF="http://www.thursby.com/"
  88 TARGET="_top"
  89 >Thursby</A
  90 > now have a CIFS Client / Server called DAVE - see</P
  91 ><P
  92 >They test it against Windows 95, Windows NT and samba for
  93 compatibility issues.  At the time of writing, DAVE was at version
  94 1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
  95 the Thursby web site (the speed of finder copies has been greatly
  96 enhanced, and there are bug-fixes included).</P
  97 ><P
  98 >
  99 Alternatives - There are two free implementations of AppleTalk for
 100 several kinds of UNIX machnes, and several more commercial ones.
 101 These products allow you to run file services and print services
 102 natively to Macintosh users, with no additional support required on
 103 the Macintosh.  The two free omplementations are
 104 <A
 105 HREF="http://www.umich.edu/~rsug/netatalk/"
 106 TARGET="_top"
 107 >Netatalk</A
 108 >, and
 109 <A
 110 HREF="http://www.cs.mu.oz.au/appletalk/atalk.html"
 111 TARGET="_top"
 112 >CAP</A
 113 >.
 114 What Samba offers MS
 115 Windows users, these packages offer to Macs.  For more info on these
 116 packages, Samba, and Linux (and other UNIX-based systems) see
 117 <A
 118 HREF="http://www.eats.com/linux_mac_win.html"
 119 TARGET="_top"
 120 >http://www.eats.com/linux_mac_win.html</A
 121 ></P
 122 ></DIV
 123 ><DIV
 124 CLASS="SECT1"
 125 ><H1
 126 CLASS="SECT1"
 127 ><A
 128 NAME="AEN3208">24.2. OS2 Client</H1
 129 ><DIV
 130 CLASS="SECT2"
 131 ><H2
 132 CLASS="SECT2"
 133 ><A
 134 NAME="AEN3210">24.2.1. How can I configure OS/2 Warp Connect or
 135                 OS/2 Warp 4 as a client for Samba?</H2
 136 ><P
 137 >A more complete answer to this question can be
 138                 found on <A
 139 HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
 140 TARGET="_top"
 141 >               http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
 142 >.</P
 143 ><P
 144 >Basically, you need three components:</P
 145 ><P
 146 ></P
 147 ><UL
 148 ><LI
 149 ><P
 150 >The File and Print Client ('IBM Peer')
 151                         </P
 152 ></LI
 153 ><LI
 154 ><P
 155 >TCP/IP ('Internet support')
 156                         </P
 157 ></LI
 158 ><LI
 159 ><P
 160 >The "NetBIOS over TCP/IP" driver ('TCPBEUI')
 161                         </P
 162 ></LI
 163 ></UL
 164 ><P
 165 >Installing the first two together with the base operating
 166                 system on a blank system is explained in the Warp manual. If Warp
 167                 has already been installed, but you now want to install the
 168                 networking support, use the "Selective Install for Networking"
 169                 object in the "System Setup" folder.</P
 170 ><P
 171 >Adding the "NetBIOS over TCP/IP" driver is not described
 172                 in the manual and just barely in the online documentation. Start
 173                 MPTS.EXE, click on OK, click on "Configure LAPS" and click
 174                 on "IBM OS/2 NETBIOS OVER TCP/IP" in  'Protocols'.  This line
 175                 is then moved to 'Current Configuration'. Select that line,
 176                 click on "Change number" and increase it from 0 to 1. Save this
 177                 configuration.</P
 178 ><P
 179 >If the Samba server(s) is not on your local subnet, you
 180                 can optionally add IP names and addresses of these servers
 181                 to the "Names List", or specify a  WINS server ('NetBIOS
 182                 Nameserver' in IBM and RFC terminology). For Warp Connect you
 183                 may need to download an update for 'IBM Peer' to bring it on
 184                 the same level as Warp 4. See the webpage mentioned above.</P
 185 ></DIV
 186 ><DIV
 187 CLASS="SECT2"
 188 ><H2
 189 CLASS="SECT2"
 190 ><A
 191 NAME="AEN3225">24.2.2. How can I configure OS/2 Warp 3 (not Connect),
 192                 OS/2 1.2, 1.3 or 2.x for Samba?</H2
 193 ><P
 194 >You can use the free Microsoft LAN Manager 2.2c Client
 195                 for OS/2 from
 196                 <A
 197 HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
 198 TARGET="_top"
 199 >               ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
 200 >.
 201         See <A
 202 HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
 203 TARGET="_top"
 204 >               http://carol.wins.uva.nl/~leeuw/lanman.html</A
 205 > for
 206                 more information on how to install and use this client. In
 207                 a nutshell, edit the file \OS2VER in the root directory of
 208                 the OS/2 boot partition and add the lines:</P
 209 ><P
 210 ><PRE
 211 CLASS="PROGRAMLISTING"
 212 >               20=setup.exe
 213                 20=netwksta.sys
 214                 20=netvdd.sys
 215                 </PRE
 216 ></P
 217 ><P
 218 >before you install the client. Also, don't use the
 219                 included NE2000 driver because it is buggy. Try the NE2000
 220                 or NS2000 driver from
 221                 <A
 222 HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
 223 TARGET="_top"
 224 >               ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
 225 > instead.
 226                 </P
 227 ></DIV
 228 ><DIV
 229 CLASS="SECT2"
 230 ><H2
 231 CLASS="SECT2"
 232 ><A
 233 NAME="AEN3234">24.2.3. Are there any other issues when OS/2 (any version)
 234                 is used as a client?</H2
 235 ><P
 236 >When you do a NET VIEW or use the "File and Print
 237                 Client Resource Browser", no Samba servers show up. This can
 238                 be fixed by a patch from <A
 239 HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
 240 TARGET="_top"
 241 >               http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
 242 >.
 243                 The patch will be included in a later version of Samba. It also
 244                 fixes a couple of other problems, such as preserving long
 245                 filenames when objects are dragged from the Workplace Shell
 246                 to the Samba server. </P
 247 ></DIV
 248 ><DIV
 249 CLASS="SECT2"
 250 ><H2
 251 CLASS="SECT2"
 252 ><A
 253 NAME="AEN3238">24.2.4. How do I get printer driver download working
 254                 for OS/2 clients?</H2
 255 ><P
 256 >First, create a share called [PRINTDRV] that is
 257                 world-readable.  Copy your OS/2 driver files there.  Note
 258                 that the .EA_ files must still be separate, so you will need
 259                 to use the original install files, and not copy an installed
 260                 driver from an OS/2 system.</P
 261 ><P
 262 >Install the NT driver first for that printer.  Then,
 263                 add to your smb.conf a parameter, os2 driver map =
 264                 <TT
 265 CLASS="REPLACEABLE"
 266 ><I
 267 >filename</I
 268 ></TT
 269 >".  Then, in the file
 270                 specified by <TT
 271 CLASS="REPLACEABLE"
 272 ><I
 273 >filename</I
 274 ></TT
 275 >, map the
 276                 name of the NT driver name to the OS/2 driver name as
 277                 follows:</P
 278 ><P
 279 ><B
 280 CLASS="COMMAND"
 281 >nt driver name = os2 "driver
 282                 name"."device name"</B
 283 >, e.g.:
 284                 HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
 285 ><P
 286 >You can have multiple drivers mapped in this file.</P
 287 ><P
 288 >If you only specify the OS/2 driver name, and not the
 289                 device name, the first attempt to download the driver will
 290                 actually download the files, but the OS/2 client will tell
 291                 you the driver is not available.  On the second attempt, it
 292                 will work.  This is fixed simply by adding the device name
 293                  to the mapping, after which it will work on the first attempt.
 294                 </P
 295 ></DIV
 296 ></DIV
 297 ><DIV
 298 CLASS="SECT1"
 299 ><H1
 300 CLASS="SECT1"
 301 ><A
 302 NAME="AEN3248">24.3. Windows for Workgroups</H1
 303 ><DIV
 304 CLASS="SECT2"
 305 ><H2
 306 CLASS="SECT2"
 307 ><A
 308 NAME="AEN3250">24.3.1. Use latest TCP/IP stack from Microsoft</H2
 309 ><P
 310 >Use the latest TCP/IP stack from microsoft if you use Windows
 311 for workgroups.</P
 312 ><P
 313 >The early TCP/IP stacks had lots of bugs.</P
 314 ><P
 315 >
 316 Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
 317 VxD drivers.  The latest release can be found on their ftp site at
 318 ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
 319 There is an update.txt file there that describes the problems that were
 320 fixed.  New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
 321 WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.</P
 322 ></DIV
 323 ><DIV
 324 CLASS="SECT2"
 325 ><H2
 326 CLASS="SECT2"
 327 ><A
 328 NAME="AEN3255">24.3.2. Delete .pwl files after password change</H2
 329 ><P
 330 >WfWg does a lousy job with passwords. I find that if I change my
 331 password on either the unix box or the PC the safest thing to do is to
 332 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
 333 ><P
 334 >
 335 If you don't do this you may find that WfWg remembers and uses the old
 336 password, even if you told it a new one.</P
 337 ><P
 338 >
 339 Often WfWg will totally ignore a password you give it in a dialog box.</P
 340 ></DIV
 341 ><DIV
 342 CLASS="SECT2"
 343 ><H2
 344 CLASS="SECT2"
 345 ><A
 346 NAME="AEN3260">24.3.3. Configure WfW password handling</H2
 347 ><P
 348 >There is a program call admincfg.exe
 349 on the last disk (disk 8) of the WFW 3.11 disk set.  To install it
 350 type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
 351 for it via the "Progam Manager" "New" Menu.  This program allows you
 352 to control how WFW handles passwords.  ie disable Password Caching etc
 353 for use with <B
 354 CLASS="COMMAND"
 355 >security = user</B
 356 ></P
 357 ></DIV
 358 ><DIV
 359 CLASS="SECT2"
 360 ><H2
 361 CLASS="SECT2"
 362 ><A
 363 NAME="AEN3264">24.3.4. Case handling of passwords</H2
 364 ><P
 365 >Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
 366 HREF="smb.conf.5.html"
 367 TARGET="_top"
 368 >smb.conf(5)</A
 369 > information on <B
 370 CLASS="COMMAND"
 371 >password level</B
 372 > to specify what characters samba should try to uppercase when checking.</P
 373 ></DIV
 374 ></DIV
 375 ><DIV
 376 CLASS="SECT1"
 377 ><H1
 378 CLASS="SECT1"
 379 ><A
 380 NAME="AEN3269">24.4. Windows '95/'98</H1
 381 ><P
 382 >When using Windows 95 OEM SR2 the following updates are recommended where Samba
 383 is being used. Please NOTE that the above change will affect you once these
 384 updates  have been installed.</P
 385 ><P
 386 >
 387 There are more updates than the ones mentioned here. You are referred to the
 388 Microsoft Web site for all currently available updates to your specific version
 389 of Windows 95.</P
 390 ><P
 391 ></P
 392 ><OL
 393 TYPE="1"
 394 ><LI
 395 ><P
 396 >Kernel Update: KRNLUPD.EXE</P
 397 ></LI
 398 ><LI
 399 ><P
 400 >Ping Fix: PINGUPD.EXE</P
 401 ></LI
 402 ><LI
 403 ><P
 404 >RPC Update: RPCRTUPD.EXE</P
 405 ></LI
 406 ><LI
 407 ><P
 408 >TCP/IP Update: VIPUPD.EXE</P
 409 ></LI
 410 ><LI
 411 ><P
 412 >Redirector Update: VRDRUPD.EXE</P
 413 ></LI
 414 ></OL
 415 ><P
 416 >Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
 417 fix may stop your machine from hanging for an extended period when exiting
 418 OutLook and you may also notice a significant speedup when accessing network
 419 neighborhood services.</P
 420 ></DIV
 421 ><DIV
 422 CLASS="SECT1"
 423 ><H1
 424 CLASS="SECT1"
 425 ><A
 426 NAME="AEN3285">24.5. Windows 2000 Service Pack 2</H1
 427 ><P
 428 >
 429 There are several annoyances with Windows 2000 SP2. One of which
 430 only appears when using a Samba server to host user profiles
 431 to Windows 2000 SP2 clients in a Windows domain.  This assumes
 432 that Samba is a member of the domain, but the problem will
 433 likely occur if it is not.</P
 434 ><P
 435 >
 436 In order to server profiles successfully to Windows 2000 SP2
 437 clients (when not operating as a PDC), Samba must have
 438 <B
 439 CLASS="COMMAND"
 440 >nt acl support = no</B
 441 >
 442 added to the file share which houses the roaming profiles.
 443 If this is not done, then the Windows 2000 SP2 client will
 444 complain about not being able to access the profile (Access
 445 Denied) and create multiple copies of it on disk (DOMAIN.user.001,
 446 DOMAIN.user.002, etc...).  See the
 447 <A
 448 HREF="smb.conf.5.html"
 449 TARGET="_top"
 450 >smb.conf(5)</A
 451 > man page
 452 for more details on this option.  Also note that the
 453 <B
 454 CLASS="COMMAND"
 455 >nt acl support</B
 456 > parameter was formally a global parameter in
 457 releases prior to Samba 2.2.2.</P
 458 ><P
 459 >
 460 The following is a minimal profile share:</P
 461 ><P
 462 ><PRE
 463 CLASS="PROGRAMLISTING"
 464 >       [profile]
 465                 path = /export/profile
 466                 create mask = 0600
 467                 directory mask = 0700
 468                 nt acl support = no
 469                 read only = no</PRE
 470 ></P
 471 ><P
 472 >The reason for this bug is that the Win2k SP2 client copies
 473 the security descriptor for the profile which contains
 474 the Samba server's SID, and not the domain SID.  The client
 475 compares the SID for SAMBA\user and realizes it is
 476 different that the one assigned to DOMAIN\user.  Hence the reason
 477 for the "access denied" message.</P
 478 ><P
 479 >By disabling the <B
 480 CLASS="COMMAND"
 481 >nt acl support</B
 482 > parameter, Samba will send
 483 the Win2k client a response to the QuerySecurityDescriptor
 484 trans2 call which causes the client to set a default ACL
 485 for the profile. This default ACL includes </P
 486 ><P
 487 ><B
 488 CLASS="COMMAND"
 489 >DOMAIN\user    "Full Control"</B
 490 ></P
 491 ><P
 492 ><SPAN
 493 CLASS="emphasis"
 494 ><I
 495 CLASS="EMPHASIS"
 496 >NOTE : This bug does not occur when using winbind to
 497 create accounts on the Samba host for Domain users.</I
 498 ></SPAN
 499 ></P
 500 ></DIV
 501 ></DIV
 502 ><DIV
 503 CLASS="NAVFOOTER"
 504 ><HR
 505 ALIGN="LEFT"
 506 WIDTH="100%"><TABLE
 507 SUMMARY="Footer navigation table"
 508 WIDTH="100%"
 509 BORDER="0"
 510 CELLPADDING="0"
 511 CELLSPACING="0"
 512 ><TR
 513 ><TD
 514 WIDTH="33%"
 515 ALIGN="left"
 516 VALIGN="top"
 517 ><A
 518 HREF="portability.html"
 519 ACCESSKEY="P"
 520 >Prev</A
 521 ></TD
 522 ><TD
 523 WIDTH="34%"
 524 ALIGN="center"
 525 VALIGN="top"
 526 ><A
 527 HREF="samba-howto-collection.html"
 528 ACCESSKEY="H"
 529 >Home</A
 530 ></TD
 531 ><TD
 532 WIDTH="33%"
 533 ALIGN="right"
 534 VALIGN="top"
 535 ><A
 536 HREF="bugreport.html"
 537 ACCESSKEY="N"
 538 >Next</A
 539 ></TD
 540 ></TR
 541 ><TR
 542 ><TD
 543 WIDTH="33%"
 544 ALIGN="left"
 545 VALIGN="top"
 546 >Portability</TD
 547 ><TD
 548 WIDTH="34%"
 549 ALIGN="center"
 550 VALIGN="top"
 551 ><A
 552 HREF="appendixes.html"
 553 ACCESSKEY="U"
 554 >Up</A
 555 ></TD
 556 ><TD
 557 WIDTH="33%"
 558 ALIGN="right"
 559 VALIGN="top"
 560 >Reporting Bugs</TD
 561 ></TR
 562 ></TABLE
 563 ></DIV
 564 ></BODY
 565 ></HTML
 566 >