X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Wed, 11 Nov 1992 09:40:30 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: TCPIP over a Token-Ring network ???????

>
> Hello novellers,
>
>  a small question which could lead to many answers:
>
>  Is it possible to run tcpip over a token-ring network?
>  By using ODI, NDIS, Packet drivers or anything else.
>  We have a Token-Ring network here with about 16 servers (2.15, 2.2, 3.11),
>  and we are planning to add a FTP server (novell 3.11 with tcpip and ftpd).
>
>  Now is it possible to bind IPX and IP to the TOKEN driver as it is done
>  when you use a NE2000 or other Ethernetboard. the System Administration
>  manual (3.11) says it is possible (page 12 and 148-).
>
>  For the workstations i have done the following:
>  autoexec.bat:
>
>  lsl            ver. 120
>  token          ver. 112
>  ipxodi         ver. 120
>  tcpip          ver. 40
>  netx           ver. 326
>
>  net.cfg:
>
>  Link Support
>       Mempool 4096                 4096 bytes for tcpip
>  Protocol
>       Bind TOKEN
>  Protocol IP
>       Bind TOKEN
>
>  Well my fileserver is still accessible so no problems there but since my
>  furthermore the tcpip.exe gives a FATAL: Error registering protocol IDs.
>  i fear the worst, tcpip is usually used in ethernet surroundings and not
>  Token-Ring.
>
>  Can somebody help me with my problem or set me straight on how i can get
>  and ftpdaemon to work on my Token-Ring based network.
>
>   signed jan verhoeven    s87405095@hse.nl
---------------
        I can give you part of the answer, and Token Ring users can give
more. The answer is yes, of course, TCP/IP applications can run over TRN.
In your case you appear to be using Lan WorkPlace/DOS v4.0. To use ODI
directly (LWP/DOS and/or Kermit) you need to list the frame type and protocol
idents in the Link Driver section of NET.CFG. This is spelled out in both
the LWP/DOS manual and the update file msr312.upd for Kermit; the LWP/DOS
manual has more info. The TCP/IP protocol ident numbers are the same as
for Ethernet (0800, 0806, 8035, for IP, ARP, RARP, resp.).
        There is more than one frame kind for Token Rings, the same as there
is more than one for Ethernet. Choose the kind which fits your environment.
        I won't discuss the sundry drivers one needs to make TRN work because
I am blissfully free of that here.
        You can put protocol shim ODIPKT on the top of ODI, but your
application will then see TRN frames and very likely it does not know what
to do with them. You can put Packet Driver IBMTOKEN on the top of TRN material
(non-ODI) to form a fake Ethernet style Packet Driver interface. You can
put protocol shim ODINSUP over ODI to form an NDIS interface.
        Again, the quickest and easiest reading material on the matter is
in the LWP/DOS manual. The most complete renditions are in the NFS manual
and even more in the detailed ODI technical specification manuals (huge things,
written for code developers, non-tutorial, but available on the net for the
brave and printer-rich folks).
        I have only Ethernet here so please don't ask me detailed TRN questions
because I haven't the fainest idea of what to suggest.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU