From 20967627378194121bc48bf387838b8bd7682478 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 16:48:14 +0000 Subject: Regenerate (This used to be commit 25db62e3101dbcae8e9daee3cb16430297afa223) --- docs/htmldocs/other-clients.html | 117 +++++++++++++++++++++------------------ 1 file changed, 64 insertions(+), 53 deletions(-) (limited to 'docs/htmldocs/other-clients.html') diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html index 7f0f99319e..4309b530ef 100644 --- a/docs/htmldocs/other-clients.html +++ b/docs/htmldocs/other-clients.html @@ -5,7 +5,7 @@ >Samba and other CIFS clientsNext

22.1. Macintosh clients?

22.1. Macintosh clients?

Yes.

22.2. OS2 Client

22.2. OS2 Client

22.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?

A more complete answer to this question can be found on

22.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?

You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from @@ -239,10 +239,10 @@ CLASS="SECT2" >

22.2.3. Are there any other issues when OS/2 (any version) - is used as a client?

When you do a NET VIEW or use the "File and Print Client Resource Browser", no Samba servers show up. This can @@ -261,10 +261,10 @@ CLASS="SECT2" >

22.2.4. How do I get printer driver download working - for OS/2 clients?

First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note @@ -274,17 +274,13 @@ NAME="AEN3350" >

Install the NT driver first for that printer. Then, add to your smb.conf a parameter, os2 driver map = - filenamefilename". Then, in the file - specified by filenamefilename, map the name of the NT driver name to the OS/2 driver name as follows:

22.3. Windows for Workgroups

22.3. Windows for Workgroups

22.3.1. Use latest TCP/IP stack from Microsoft

22.3.1. Use latest TCP/IP stack from Microsoft

Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.

22.3.2. Delete .pwl files after password change

22.3.2. Delete .pwl files after password change

WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -362,9 +358,9 @@ CLASS="SECT2" >

22.3.3. Configure WfW password handling

22.3.3. Configure WfW password handling

There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -381,9 +377,9 @@ CLASS="SECT2" >

22.3.4. Case handling of passwords

22.3.4. Case handling of passwords

Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the password level to specify what characters samba should try to uppercase when checking.

22.3.5. Use TCP/IP as default protocol

To support print queue reporting you may find +that you have to use TCP/IP as the default protocol under +WfWg. For some reason if you leave Netbeui as the default +it may break the print queue reporting on some systems. +It is presumably a WfWg bug.

22.4. Windows '95/'98

22.4. Windows '95/'98

When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -448,9 +459,9 @@ CLASS="SECT1" >

22.5. Windows 2000 Service Pack 2

22.5. Windows 2000 Service Pack 2

There are several annoyances with Windows 2000 SP2. One of which @@ -560,7 +571,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextReporting BugsHow to compile SAMBA