🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.programmer
Article #2032

Re: Novell OS/2 2.0 Requester

#2032
From: John Lautmann
Date: Mon, 12 Oct 1992 10:58
304 lines
8952 bytes
In article <Bv9Lu3.9CL@virtech.uucp> rickr@virtech.uucp (Rick Rodman) writes:
>I'm having funny problems with the Novell Netware OS/2 Requester.
>
>I can't get it to work on my home LAN with Extended Services using LANSUP
>or ODINSUP.  Extended Services still works with RDS (NetBIOS) when I use
>LANSUP and the IBMTOK driver, but with Novell's TOKEN.SYS, Extended Services
>won't work.
>
>The symptom is the usual one, NW0015: Error getting connection ID (0x880F).
>
>Now, Novell never documents any error messages in the  manual, and, when I
>call them, says they require $150 before they'll listen to me.  (As I replied,
>they have an interesting, albeit self-serving, concept of who is supporting
>whom.)
>
>I have gotten this requester to work with ODINSUP and TOKEN.SYS, but not
>with LANSUP, at another seemingly identical Token-Ring LAN!
>
>Does anyone out there have any ideas as to what I might try?  This is an
>ISA bus machine with 16/4 ISA board, 33MHz 386, OS/2 2.0, Extended Services.
>
>-- 
>
>Rick Rodman      uunet!virtech!rickr	Manassas, VA
>"This government is the biggest fraud in the history of the industrialized
>Western world.  There isn't any Western democracy that does so little for its

I have been able to use the netware requester using both odinsup and lansup.
I have been told that the net.cfg needs to have a blank line at the end.
If you are using a Locally administered address the one in the net.cfg
must match th one in protocol.ini

Here is an example for the config.sys, protocol.ini and net.cfg to use in 
order to use netware requester and lansup:



LANSUP.SYS: the alternative to ODINSUP....

LANSUP.SYS relies on the NDIS drivers to control the lan adapter,
whereas ODINSUP uses the ODI drivers to control the card. LANSUP
replaces CMGRLAN.SYS and provides the same functionality. LANSUP
supports two of the four commonly used ethernet frame types:
ETHERNET_802.3 & ETHERNET_II frames are no longer supported. This
is due to a change in LANDD.OS2. 

In a nut shell, LANSUP is used when you do not have an ODI
compliant MLID driver for the physical adapter in the workstation.
ODINSUP is used when you have an NDIS compliant driver (example,
TOKEN.SYS).

LANSUP is compatible with IBM's LS (lan services) v2.0 and ES
(extended services) v1.0. It can also be used with OS/2 EE v1.3.

CONFIGURATION:      

Load ES and LS first in config.sys (see example below). Replace the
MLID driver with LANSUP.SYS. Specify the frame type in the NET.CFG
file (at least one frame type is required). Reboot the workstation
for the changes to take effect.

            ****************** NOTE **********************

You must include the NODE ADDRESS in the NET.CFG. If the address
is unknown, a dummy number is used initially. This dummy number
must be 12 characters long followed by the letter L or M.

The first time the NET.CFG loads, an error will be displayed
informing the user of the correct node number that needs to be
used. Write that number down and then edit the NET.CFG and replace
the dummy number with correct node address.

            ***********************************************

CONFIG.SYS using LANSUP, ES, LS, and OS/2 NetWare Requester:

IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;.;C:\OS2\DLL;C:\OS2\MDOS;C
:\CMLIB\DLL;C:\;C:\OS2\APPS\DLL;C:\ibmcom\dll;C:\NETWARE;




SET
PATH=C:\IBMLAN\NETPROG;C:\OS2;C:\MUGLIB;C:\OS2\SYSTEM;C:\OS2\MDOS
\WINOS2;C:\CMLIB;C:\CMLIB\APPN;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\
OS2\APPS;C:\NETWARE;
SET
DPATH=C:\IBMLAN\NETPROG;C:\IBMLAN;C:\OS2;C:\MUGLIB\DLL;C:\CMLIB;C
:\CMLIB\APPN;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;
C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\ibmcom;
SET PROMPT=$i
$pY
SET HELP=C:\CMLIB\APPN;C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=C:\ibmcom\lanmsgdd.os2 /I:C:\ibmcom
DEVICE=C:\ibmcom\protman.os2 /I:C:\ibmcom
DEVICE=C:\ibmcom\protocol\LANDD.OS2
DEVICE=C:\ibmcom\protocol\LANDLLDD.OS2
DEVICE=C:\OS2\R0CSDD.SYS
DEVICE=C:\OS2\TESTCFG.SYS
DEVICE=C:\OS2\DOS.SYS
DEVICE=C:\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=512,LW
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 2048
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;
BASEDEV=PRINT02.SYS
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2SCSI.ADD /LED
BASEDEV=OS2SCSI.DMD
BASEDEV=OS2DASD.DMD
SET BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK;
SET EPATH=C:\OS2\APPS
REM DEVICE=C:\OS2\APPS\SASYNCDB.SYS
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /P
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VCDROM.SYS
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP




SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA)
DEVICE=C:\OS2\MDOS\VVGA.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS
DEVICE=C:\OS2\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
DEVICE=C:\CMLIB\DFTDD.SYS
DEVICE=C:\CMLIB\ACSLDLAN.SYS
RUN=C:\ibmcom\protocol\landll.exe
RUN=C:\ibmcom\protocol\netbind.exe
RUN=C:\ibmcom\lanmsgex.exe
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200

DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
DEVICE=C:\CMLIB\APPN\CMKFMDE.SYS
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
RUN=C:\OS2\SYSTEM\LOGDAEM.EXE
DEVICE=C:\OS2\LOG.SYS

REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
rem DEVICE=C:\NETWARE\TOKEN.SYS
DEVICE=C:\NETWARE\LANSUP.SYS
DEVICE=C:\NETWARE\ROUTE.SYS
DEVICE=C:\NETWARE\IPX.SYS
rem DEVICE=C:\NETWARE\SPX.SYS
rem RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
REM --- NetWare Requester statements END ---

IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N

NET.CFG

LINK SUPPORT
    BUFFERS 15 1130




LINK DRIVER LANSUP
    FRAME TOKEN-RING
    FRAME TOKEN-RING_SNAP
    NODE ADDRESS 4000002008A8

NETWARE REQUESTER
    PREFERRED AUSL11NW311-1


PROTOCOL.INI - Notice no changes to the bindings statements


PROT_MANY
 DriverName = PROTMAN$


IBMLXCFGY
 IBMTOK_nif = IBMTOK.nif
 LANDD_nif = LANDD.nif
 NETBEUI_nif = NETBEUI.nif

;*----------------------------------------------*
;*------------- PROTOCOL SECTION ---------------*
;*----------------------------------------------*


LANDD_nifY
 DriverName = LANDD$
 Bindings = IBMTOK_nif
 NETADDRESS = "T4000002008A8"
 ETHERAND_TYPE = "I"
 SYSTEM_KEY = 0x0
 OPEN_OPTIONS = 0x2000
 TRACE = 0x0
 LINKS = 40
 MAX_SAPS = 7
 MAX_G_SAPS = 0
 USERS = 4
 TI_TICK_G1 = 255
 T1_TICK_G1 = 15
 T2_TICK_G1 = 3
 TI_TICK_G2 = 255
 T1_TICK_G2 = 25
 T2_TICK_G2 = 10
 IPACKETS = 250
 UIPACKETS = 100
 MAXTRANSMITS = 6
 MINTRANSMITS = 2
 TCBS = 64
 GDTS = 30
 ELEMENTS = 800








NETBEUI_nifY
 DriverName = netbeui$
 Bindings = IBMTOK_nif
 ETHERAND_TYPE = "I"
 USEADDRREV = "YES"
 SESSIONS = 40
 NCBS = 95
 NAMES = 21
 SELECTORS = 5
 USEMAXDATAGRAM = "NO"
 ADAPTRATE = 1000
 WINDOWERRORS = 0
 TI = 30600
 T1 = 3000
 T2 = 240
 MAXIN = 1
 MAXOUT = 2
 NETBIOSTIMEOUT = 500
 NETBIOSRETRIES = 8
 NAMECACHE = 0
 PIGGYBACKACKS = 1
 DATAGRAMPACKETS = 2
 PACKETS = 350
 PIPELINE = 5
 MAXTRANSMITS = 6
 MINTRANSMITS = 2
 DLCRETRIES = 5


;*----------------------------------------------*
;*--------------- MAC SECTION ------------------*
;*----------------------------------------------*



IBMTOK_nifY
 DriverName = IBMTOK$
 MAXTRANSMITS = 12
 RECVBUFS = 47
 RECVBUFSIZE = 256
 XMITBUFS = 1
 XMITBUFSIZE = 1968
Technical Details
Message-ID: <2589@cronos.metaphor.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!cs.utexas.edu!sun-barr!decwrl!nntp1.radiomail.net!cronos!mettech1!jlautman
References: <Bv9Lu3.9CL@virtech.uucp>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!cs.utexas.edu!sun-barr!decwrl!nntp1.radiomail.net!cronos!mettech1!jlautman
From: jlautman@mettech1.metaphor.com (John Lautmann)
Newsgroups: comp.os.os2.programmer,comp.os.os2
Subject: Re: Novell OS/2 2.0 Requester
Keywords: help, problems
Message-ID: <2589@cronos.metaphor.com>
Date: 12 Oct 92 10:58:42 GMT
References: <Bv9Lu3.9CL@virtech.uucp>
Sender: news@cronos.metaphor.com
Followup-To: comp.os.os2.programmer
Organization: Metaphor Computer Systems, Mountain View, CA
Lines: 318