1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Samba and other CIFS clients</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
10 TITLE="SAMBA Project Documentation"
11 HREF="samba-howto-collection.html"><LINK
14 HREF="p3106.html"><LINK
17 HREF="portability.html"><LINK
19 TITLE="Reporting Bugs"
20 HREF="bugreport.html"></HEAD
31 SUMMARY="Header navigation table"
40 >SAMBA Project Documentation</TH
48 HREF="portability.html"
77 >Chapter 24. Samba and other CIFS clients</H1
79 >This chapter contains client-specific information.</P
87 >24.1. Macintosh clients?</H1
90 HREF="http://www.thursby.com/"
93 > now have a CIFS Client / Server called DAVE - see</P
95 >They test it against Windows 95, Windows NT and samba for
96 compatibility issues. At the time of writing, DAVE was at version
97 1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
98 the Thursby web site (the speed of finder copies has been greatly
99 enhanced, and there are bug-fixes included).</P
102 Alternatives - There are two free implementations of AppleTalk for
103 several kinds of UNIX machnes, and several more commercial ones.
104 These products allow you to run file services and print services
105 natively to Macintosh users, with no additional support required on
106 the Macintosh. The two free omplementations are
108 HREF="http://www.umich.edu/~rsug/netatalk/"
113 HREF="http://www.cs.mu.oz.au/appletalk/atalk.html"
118 Windows users, these packages offer to Macs. For more info on these
119 packages, Samba, and Linux (and other UNIX-based systems) see
121 HREF="http://www.eats.com/linux_mac_win.html"
123 >http://www.eats.com/linux_mac_win.html</A
133 >24.2. OS2 Client</H1
141 >24.2.1. How can I configure OS/2 Warp Connect or
142 OS/2 Warp 4 as a client for Samba?</H2
144 >A more complete answer to this question can be
146 HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
148 > http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
151 >Basically, you need three components:</P
157 >The File and Print Client ('IBM Peer')
162 >TCP/IP ('Internet support')
167 >The "NetBIOS over TCP/IP" driver ('TCPBEUI')
172 >Installing the first two together with the base operating
173 system on a blank system is explained in the Warp manual. If Warp
174 has already been installed, but you now want to install the
175 networking support, use the "Selective Install for Networking"
176 object in the "System Setup" folder.</P
178 >Adding the "NetBIOS over TCP/IP" driver is not described
179 in the manual and just barely in the online documentation. Start
180 MPTS.EXE, click on OK, click on "Configure LAPS" and click
181 on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line
182 is then moved to 'Current Configuration'. Select that line,
183 click on "Change number" and increase it from 0 to 1. Save this
186 >If the Samba server(s) is not on your local subnet, you
187 can optionally add IP names and addresses of these servers
188 to the "Names List", or specify a WINS server ('NetBIOS
189 Nameserver' in IBM and RFC terminology). For Warp Connect you
190 may need to download an update for 'IBM Peer' to bring it on
191 the same level as Warp 4. See the webpage mentioned above.</P
200 >24.2.2. How can I configure OS/2 Warp 3 (not Connect),
201 OS/2 1.2, 1.3 or 2.x for Samba?</H2
203 >You can use the free Microsoft LAN Manager 2.2c Client
206 HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
208 > ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
211 HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
213 > http://carol.wins.uva.nl/~leeuw/lanman.html</A
215 more information on how to install and use this client. In
216 a nutshell, edit the file \OS2VER in the root directory of
217 the OS/2 boot partition and add the lines:</P
220 CLASS="PROGRAMLISTING"
227 >before you install the client. Also, don't use the
228 included NE2000 driver because it is buggy. Try the NE2000
229 or NS2000 driver from
231 HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
233 > ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
244 >24.2.3. Are there any other issues when OS/2 (any version)
245 is used as a client?</H2
247 >When you do a NET VIEW or use the "File and Print
248 Client Resource Browser", no Samba servers show up. This can
249 be fixed by a patch from <A
250 HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
252 > http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
254 The patch will be included in a later version of Samba. It also
255 fixes a couple of other problems, such as preserving long
256 filenames when objects are dragged from the Workplace Shell
257 to the Samba server. </P
266 >24.2.4. How do I get printer driver download working
267 for OS/2 clients?</H2
269 >First, create a share called [PRINTDRV] that is
270 world-readable. Copy your OS/2 driver files there. Note
271 that the .EA_ files must still be separate, so you will need
272 to use the original install files, and not copy an installed
273 driver from an OS/2 system.</P
275 >Install the NT driver first for that printer. Then,
276 add to your smb.conf a parameter, os2 driver map =
282 >". Then, in the file
289 name of the NT driver name to the OS/2 driver name as
294 >nt driver name = os2 "driver
295 name"."device name"</B
297 HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
299 >You can have multiple drivers mapped in this file.</P
301 >If you only specify the OS/2 driver name, and not the
302 device name, the first attempt to download the driver will
303 actually download the files, but the OS/2 client will tell
304 you the driver is not available. On the second attempt, it
305 will work. This is fixed simply by adding the device name
306 to the mapping, after which it will work on the first attempt.
317 >24.3. Windows for Workgroups</H1
325 >24.3.1. Use latest TCP/IP stack from Microsoft</H2
327 >Use the latest TCP/IP stack from microsoft if you use Windows
330 >The early TCP/IP stacks had lots of bugs.</P
333 Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
334 VxD drivers. The latest release can be found on their ftp site at
335 ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
336 There is an update.txt file there that describes the problems that were
337 fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
338 WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.</P
347 >24.3.2. Delete .pwl files after password change</H2
349 >WfWg does a lousy job with passwords. I find that if I change my
350 password on either the unix box or the PC the safest thing to do is to
351 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
354 If you don't do this you may find that WfWg remembers and uses the old
355 password, even if you told it a new one.</P
358 Often WfWg will totally ignore a password you give it in a dialog box.</P
367 >24.3.3. Configure WfW password handling</H2
369 >There is a program call admincfg.exe
370 on the last disk (disk 8) of the WFW 3.11 disk set. To install it
371 type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
372 for it via the "Progam Manager" "New" Menu. This program allows you
373 to control how WFW handles passwords. ie disable Password Caching etc
386 >24.3.4. Case handling of passwords</H2
388 >Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
389 HREF="smb.conf.5.html"
395 > to specify what characters samba should try to uppercase when checking.</P
405 >24.4. Windows '95/'98</H1
407 >When using Windows 95 OEM SR2 the following updates are recommended where Samba
408 is being used. Please NOTE that the above change will affect you once these
409 updates have been installed.</P
412 There are more updates than the ones mentioned here. You are referred to the
413 Microsoft Web site for all currently available updates to your specific version
421 >Kernel Update: KRNLUPD.EXE</P
425 >Ping Fix: PINGUPD.EXE</P
429 >RPC Update: RPCRTUPD.EXE</P
433 >TCP/IP Update: VIPUPD.EXE</P
437 >Redirector Update: VRDRUPD.EXE</P
441 >Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
442 fix may stop your machine from hanging for an extended period when exiting
443 OutLook and you may also notice a significant speedup when accessing network
444 neighborhood services.</P
453 >24.5. Windows 2000 Service Pack 2</H1
456 There are several annoyances with Windows 2000 SP2. One of which
457 only appears when using a Samba server to host user profiles
458 to Windows 2000 SP2 clients in a Windows domain. This assumes
459 that Samba is a member of the domain, but the problem will
460 likely occur if it is not.</P
463 In order to server profiles successfully to Windows 2000 SP2
464 clients (when not operating as a PDC), Samba must have
467 >nt acl support = no</B
469 added to the file share which houses the roaming profiles.
470 If this is not done, then the Windows 2000 SP2 client will
471 complain about not being able to access the profile (Access
472 Denied) and create multiple copies of it on disk (DOMAIN.user.001,
473 DOMAIN.user.002, etc...). See the
475 HREF="smb.conf.5.html"
479 for more details on this option. Also note that the
483 > parameter was formally a global parameter in
484 releases prior to Samba 2.2.2.</P
487 The following is a minimal profile share:</P
490 CLASS="PROGRAMLISTING"
492 path = /export/profile
494 directory mask = 0700
499 >The reason for this bug is that the Win2k SP2 client copies
500 the security descriptor for the profile which contains
501 the Samba server's SID, and not the domain SID. The client
502 compares the SID for SAMBA\user and realizes it is
503 different that the one assigned to DOMAIN\user. Hence the reason
504 for the "access denied" message.</P
509 > parameter, Samba will send
510 the Win2k client a response to the QuerySecurityDescriptor
511 trans2 call which causes the client to set a default ACL
512 for the profile. This default ACL includes </P
516 >DOMAIN\user "Full Control"</B
523 >NOTE : This bug does not occur when using winbind to
524 create accounts on the Samba host for Domain users.</I
534 SUMMARY="Footer navigation table"
545 HREF="portability.html"
554 HREF="samba-howto-collection.html"
563 HREF="bugreport.html"