-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- PRODUCT: AI-ODI.EXE -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Overview: AI-ODI.EXE is a program that binds Artisoft's AILANBIOS protocol directly to an ODI driver. AI-ODI can be used in place of AI-NDIS, PROTMAN, and ODINSUP. An ODI low level adapter driver is also required in place of the NDIS adapter driver. By using IPX Routing, AI-ODI allows the packets sent by the workstation to be passed by an IPX router and then acted upon by another IPX-routed LANtastic machine on the other side of the router. Requirements: These requirements assume that Noderunner adapters are in the workstation. If a different adapter is used, substitute the adapter's ODI driver for NRODI in AUTOEXEC.BAT and modify the LINK DRIVER section of NET.CFG accordingly to recognize the different card. Workstation: LSL.COM NRODI.COM IPXODI.COM (Optional, needed only if configuring for NCP. See IPX_ROUTING section of this appnote.) AI-ODI.EXE AILANBIO.EXE REDIR.EXE NET.CFG NET.EXE Server: Setup will vary depending on the type of server. Be aware of frame types, make sure they match on the server and the workstation. Usage: 1. Copy all files to the \LANTASTI subdirectory, or whichever directory LANtastic programs reside. 2. Edit NET.CFG, specifying the frame type compatible with your network. The frame type specifier is altered by changing the BIND #x line, where x denotes the line in the "LINK DRIVER " section that sets the frame type (See the sample NET.CFG below). Note that ETHERNET_II is listed first. The AI-ODI program will bind to either the first frame type listed in the NET.CFG file or one that is specified under a PROTOCOL AI-ODI section. The only frame types that AI-ODI will recognize are ETHERNET_II or ETHERNET_802.3. LANtastic natively uses the ETHERNET_II protocol and this choice should be used for a standard LANtastic configuration. See the IPX Routing section of this appnote if LANtastic is to be configured using the ETHERNET_802.3 protocol. This sample NET.CFG also shows how the IPX protocol can also be loaded and bound to the low-level card driver. IPX can be bound to any frametype listed in the NET.CFG as long as it is not the same frametype associated with AI-ODI. This sample NET.CFG shows IPX being bound to the ETHERNET_802.3 frame type. This is acceptable because AI-ODI is using ETHERNET_II. If IPX is bound here to #1 (ETHERNET_II, the same frame as AI-ODI) then a situation would arise where the low-level driver would not know how to send the appropriate packet to the correct handler and the workstation would not be able to communicate with other LANtastic nodes. Binding IPX to the low-level driver would usually be done for an NCP connection where this frametype is used on the NetWare server. 3. Load drivers in the following order, being sure that all previous network drivers are removed from config.sys, autoexec.bat, or startnet.bat: a) LSL.COM b) NRODI.COM c) AI-ODI.EXE d) IPXODI.COM (Optional. Used for NCP connectivity.) e) AILANBIO.EXE f) REDIR.EXE 4. Run LANCHECK on the ODI machine and at least two others on the network for an interconnectivity check to ensure that all machines are speaking to each other. Sample Config Files for a standard or NCP connection using Ethernet: --------------------------------------------------------------------- Workstation: NET.CFG PROTOCOL IPX BIND #2 PROTOCOL AI-ODI BIND #1 LINK DRIVER NRODI FRAME ETHERNET_II FRAME ETHERNET_802.2 CONFIG.SYS DEVICE=HIMEM.SYS DEVICE=EMM386.EXE NOEMS FILES=50 BUFFERS=32 AUTOEXEC.BAT PATH ... PROMPT $P$G LSL NRODI AI-ODI IPXODI (Optional. Required for NCP connection) AILANBIO REDIR /NCP (NCP switch used only for NCP connection) NET LOGIN ... SET COMSPEC=C:\DOS\COMMAND.COM IPX Routing ----------- IPX Routing changes the native LANtastic packet header into an IPX type header. This allows LANtastic packets to cross an IPX router such as a Novell MultiProtocol Router, or any other routers that pass IPX packets. However, A few issues arise that must be kept in mind. By configuring a workstation to use IPX routing, it then communicates over the Ethernet 802.3 protocol. The NET.CFG must also then be configured such that AI-ODI will be able to bind to the ETHERNET_802.3 frametype. Also, all LANtastic workstations that will communicate with a node configured for IPX_Routing must also be configured for IPX_Routing. It is not necessary for an IPX_Routed workstation to use AI-ODI. The native LANtastic drivers can be configured by using the /IEEE and IPX_ROUTING switches on the low-level driver and on AILANBIO. WARNING--If IPXODI is loaded, it must NOT bind to the ETHERNET_802.3 frametype. This causes a protocol conflict and will cause the workstation to not be able to "see" the rest of the network. Any other frame types should be okay. Sample Configuration Files for an IPX Routing configuration: ------------------------------------------------------------ Workstation: NET.CFG PROTOCOL IPX BIND #2 PROTOCOL AI-ODI BIND #1 LINK DRIVER NRODI FRAME ETHERNET_802.3 FRAME ETHERNET_802.2 CONFIG.SYS DEVICE=HIMEM.SYS DEVICE=EMM386.EXE NOEMS FILES=50 BUFFERS=32 AUTOEXEC.BAT PATH ... PROMPT $P$G LSL NRODI AI-ODI/IPX_ROUTING IPXODI (Optional. Required for NCP connection.) AILANBIO/IPX_ROUTING REDIR /NCP (NCP switch optional) NET LOGIN ... NET USE ... SET COMSPEC=C:\COMMAND.COM -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- If you have any difficulties, please contact Artisoft Technical Support at (520) 670-7000. Brand names are trademarks or registered trademarks of their respective companies. LANtastic is a trademark of Artisoft, Inc. All rights reserved. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-