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