1
0
mirror of https://github.com/samba-team/samba.git synced 2025-03-09 08:58:35 +03:00

Way out of date. Dan

(This used to be commit dc395e3515a4ef90af9e602be2bc0a6ce25627f6)
This commit is contained in:
Samba Release Account 1997-08-26 01:31:32 +00:00
parent 41bbc5e21f
commit 90adbac6de
3 changed files with 0 additions and 249 deletions

View File

@ -1,59 +0,0 @@
Author: riiber@oslonett.no
Date: Unknown
Status: Unspecified Currency - feedback welcomed
Subject: This describes how to use smbclient to connect to an OS/2 server.
Knowing this allows you to use a OS/2 printer from unix.
==============================================================================
How to login to an OS/2 server
-------------------------------
Sample setup for OS/2 server running LanMan 2.2:
OS/2 Server Name : \\OBV11
OS/2 User Account : ARNE
OS/2 Password : xxx
OS/2 shared service 1 : LASER02
OS/2 Shared service 2 : PCPROGS
Samba NetBIOS name : KLATREMUS
First, the two servers were started with the commands
smbd and nmbd -n KLATREMUS.
Command to connect to a the shared printer LASER02 on the OS/2 server:
smbclient '\\OBV11\LASER02' xxx -n ARNE -U ARNE -P
and to connect to the shared drive 'PCPROGS':
smbclient '\\OBV11\PCPROGS' xxx -n ARNE -U ARNE
If login to the OS/2 server fails:
----------------------------------
The remarkable OS/2 server requires NetBIOS name to be equal to User name.
This was the only combination of (NetBIOS name, User name) that allowed login.
Password xxx must be in upper case, case in user name is unimportant.
The OS/2 server responds with "Bad password - name/password pair"
if the password is illegal (in lowercase, for example).
If correct user name and password, but invalid NetBIOS name is given,
it responds with "... SMBtcon failed. ERRDOS - 65".
The OS/2 server can disable login from a list of workstations (PCs)
corresponding to the NetBIOS name (-n option). I set it up to
allow login from any workstation.
(I experimented quite a lot with the -U and -n options, printed and browsed
the MS SMB protocol docs and the RFC's, then read some comp.protocols.smb,
got some tips, tried some "stupid" command line options,
and at last I got it working!)
-Arne-

View File

@ -1,87 +0,0 @@
Contributor: Jason Rumney <jasonr@pec.co.nz>.
Date: 1995
Status: Needs Updating - Old!
Subject: IBM OS/2 Support
=============================================================================
Samba 1.9.15p8 for OS/2 : REQUIRES emx 0.9b.
Please read the file README, which contains general information about
the configuration and use of Samba.
Notes specific to OS/2 port:
============================
Filenames have been shortened to 8.3 in case anyone is using FAT.
Files affected are:
smb.conf -> smb.cfg smbclient -> smbclnt.exe
smbstatus -> smbstat.exe nmblookup -> nmblook.exe
As I only use HPFS, I can't guarantee this will work on FAT systems,
although I have tried to stick to 8.3 filenames. I have noticed some
temporary files being created with long filenames by smbd when I tried
printing (which does not work yet anyway). nmbd will not be able to
create browse lists on FAT systems, as it uses temporary files with
long file names.
smb.cfg should be in the directory smbd is started from. The path to
smb.cfg is a compile time option, so if you are compiling from source
you can set this to an absolute path to remove this restriction.
User home directories not supported. This doesn't make much sense on
OS/2. I haven't actually disabled anything, so if you try setting
this up, behaivour is undefined.
Password support is incomplete (I have found a crypt() routine, but
lack of passwd file support in the EMX libraries make support difficult
without major changes).
Printing does not appear to be working. OS/2's lpq gives output in a
different format than the versions of lpq already supported by samba.
This will be easy to accomodate, but there is not much point until I can
get lpr working properly.
Source is available from the Samba WWW site :
http://samba.canberra.edu.au/pub/samba/
EMX 0.9b is available from hobbes.nmsu.edu, ftp.cdrom.com, ftp.leo.org and
other OS/2 FTP sites. emxrt.zip contains the required libraries.
Bugs:
=====
Known problems:
===============
Printing does not work. I have tried using REXX scripts with path info
built in, and watched the processes startup properly but nothing comes
out of the printer (remote via lpr in this case).
If you can get it going, please let me know how you did it.
The output from OS/2's lpq.exe is not understood by smbd, so all querys
about the print queue say it is empty. Printing doesn't work anyway,
so I have not attempted to fix this yet.
Temporary files are created with long filenames (when printing, and updating
browse list)
Bug reports for the OS/2 port should be sent to Jason Rumney <jasonr@pec.co.nz>.
Change log:
===========
Changes from release 1 to release 2.
nmblookup (nmblook.exe) is included, and works.
An attempt at password support was made using the gnuufc crypt routines,
but then I found that a lot of functions in the EMX libraries to do with
passwd files don't actually do anything.
Browse lists should now work if you use HPFS and set your lock directory
to an absolute pathname.

View File

@ -1,103 +0,0 @@
Contributor: Wade Maxfie <maxfield@ctelcom.uucp.netcom.com>
Date: Unknown
Status: Old
Subject: Samba with OS/2 Warp.
============================================================================
Note that you may also find ftp://ftp.cdrom.com/pub/os2/new/os2net.faq
useful.
Can I use Samba with Warp?
Yes. The MSClient software at ftp.microsoft.com in the Bussys
(lanman os2 directory) will work, sort of. It is version 2.2c.
First, uncloack os2ver. (attrib -h -r -s c:\os2ver). It is a
text file. change netwksta.xxx to 20=netwksta.sys. Also add
20=setup.exe. Another change will be needed, a .vdd file. I remember
it came up during the installation as being a wrong version. I wrote
the name down, changed os2ver to include it, and restarted the
installation.
Here is a copy of my os2ver
setup.exe
netbios.os2
nwifs.ifs
netwksta.sys
nwreq.sys
netbios.sys
ipx.sys
netvdd.sys
Re-cloak os2ver. (attrib +h +r +s c:\os2ver)
Run the installation from an OS/2 Box. Note that your mouse wont work,
use the TAB key to move around, enter to select hilighted items.
Here is a copy of my Config.sys file regarding the Laman entries.
Note even though the version is 2.2c, it reports 2.2a in the text.
REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.
DEVICE=C:\LANMAN\DRIVERS\PROTMAN\PROTMAN.OS2 /i:C:\LANMAN
DEVICE=C:\LANMAN\DRIVERS\ETHERNET\Ns2000\Ns2000.OS2
RUN=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\starttcp.exe
RUN=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\startnb.exe
DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\tcpdrv.os2
DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\nbdrv.os2
DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\nmdrv.os2
DEVICE=C:\LANMAN\arpa\sockdrv.os2
DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.OS2
DEVICE=C:\LANMAN\NETPROG\RDRHELP.SYS
IFS=C:\LANMAN\NETPROG\NETWKSTA.SYS /i:C:\LANMAN
DEVICE=C:\LANMAN\NETPROG\NETVDD.SYS
REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.
If you have an NE2000 card, don't reboot, or you'll be sorry.
enable the automatic backup mechanism for recovering old config.sys and
other files in OS/2. It paid for itself during this installation nightm
before I knew better!)
Next, (or perhaps before this), if you have an NE2000 adaptor,
get the ns2000 files from hobbes.nmsu.edu (in ns2000.zip). I manually
patched protocol.ini to refer to that adaptor, and copied it into my
c:\lanman directory. Note that I also modified the driver to be loaded
in the config.sys to the ns2000.os2. It might install as an "other"
adaptor.
A command file "startup.cmd" is placed in c:\. This file is
automatically run when OS/2 Warp starts.
Here is a copy of my startup file. Note that Warp sometimes fails to
login properly to the server. I solve this by checking for the
existance of a file, and rerunning the loing if that file fails to
exist.
@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
NET START WORKSTATION
:relogin
NET LOGON maxfield mypassword /y
rem net use f: \\packard90\d$
rem net use g: \\linuxone\cdromsdir
rem net use h: \\linuxone\public
:doOver
if not exist f:\wildcat\wildcat.exe goto relogin
@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
exit
Finally, the system expects to be on a domain with a domain
server. BTW, TCP/IP and NetBeui allow simultaneous communication with
Os/2 lanserver 4.0, and Samba. (Note: Lanserver 4.0 won't yet to
TCP/IP. (Well,it might, but it crashes before I get to that point, so I
havent' been able to enable it))
I have not yet tried with only a SAMBA server on the domain.
I would be glad to try to answer any questions at above e-mail
address, if I can.
wade