The AUI Connector
 

Original artwork by 3com

AUI  Pin Assignments Pin  Function Pin Function 1  Collision shield 9 Collision – 2  Collision + 10 Transmit – 3 Transmit + 11 Transmit shield 4  Receive shield 12 Receive – 5  Receive + 13 +12 volts 6  Power return 14 Voltage shield 7 Not used 15 Not used 8 Not used

Ethernet vs. token ring networks
    Token Ring is single access, meaning there is only one token. Thus, at any given time only one station is able to use the LAN. Since there is no such thing as a collision, all 4 or 16 Mbs can be used for frame transmission. This means that Ethernet with a practical utilization level of around 40% provides the same theoretically amount of bandwidth as 4Mbs token ring and 25% the bandwidth of 16Mbs token ring. 
    In terms of how much user data can theoretically be passed on the network per frame, the ratio between overhead and MTU is the best measure. For Ethernet it is 26/1518 = .017, for token ring it is 21/18000=.0012. This means that in the best case scenario, token ring transmits frames with one tenth the overhead associated with a similar transfer of Ethernet. 

TR Diagnostic   A network diagnostics program for tracking down token-ring faults. Screen shot
   The PC on which you run the diagnostic software must use the IBM LAN Support Program (DXMA0MOD.SYS and DXMC0MOD.SYS device drivers) or an equivalent.

IBM Networking LAN Adapter Support   Lan Support Program is on this page.

LANAIDC command line parameters

NetWare Requesters/Servers Drop Sessions across Cisco Routers
   When an idle workstation is being queried by a NetWare server with IPX watchdog packets, the Cisco router does not update the timestamp in the RIF cache. When this happens and the router does not know where to send the watchdog packets, it sends out an LLC XID test frame to obtain a route. 
   Some stations respond to this frame (non-turbo shared RAM adapters with on-board LLC or DMA/busmaster adapters that have an 802.2 protocol loaded in the workstation) but many (DMA/busmaster adapters with no 802.2 protocol loaded) do not. The NetWare server continues to send IPX watchdog packets with no response and eventually the server terminates the connection.

This problem can be resolved by performing any of the following corrective actions:
-Turn off multi-ring support for the Cisco router. This is acceptable if the Cisco router is routing and not bridging also.
-Set the Cisco RIF table addresses to Static. This may or may not be acceptable depending upon the network. This would eliminate the router  software from timing out the RIF cache entry.
-Configure the NetWare Server watchdog packets. On NetWare 4.1 they default to first packet after 5 minutes idle and can be set from 1 minute to 14 days.
-Upgrade to 10(3) level of software for the Cisco router. This could mean hardware upgrade for "old routers".
-Configure an active LLC 802.2 protocol driver in the workstation:
     Win95, Win98, WinNT - Load NetBEUI and MSDLC32 protocols.
     DOS/Win 3.X - Use LAN Support Program or LAN Client with LLC protocol configured.
     OS/2 - configure the 802.2 protocol (LANDD) in MPTS.
     NetWare Server - Use Novell's IEEE8022.NLM.

Flash Capable Streamers
The LANStreamer MC32 and LANStreamer MC16 adapters used EPROMs; they
are not user upgradable.. Later adapters in the Streamer Family of adapters use FLASH memory to
store the microcode; they can be upgraded by the user.

SUPPORTED ADAPTERS AND MICROCODE LEVELS:

Adapter	CURRENT	PREVIOUS
- IBM EtherStreamer MC 32	C0	B3AC
- IBM Dual EtherStreamer MC 32	C0	B3
- IBM Auto LANStreamer MC 32	D0	C3 B4 B3
- IBM Dual LANStreamer MC 32	D0	C3 B3

MICROCODE LEVELS:
   The microcode has a common base and evolves; therefore, changes are cumulative. Some changes are based on adding new adapters to the Streamer family (adding PCI adapters, multi port adapters). Significant functional changes between levels are as follows.

AC --> B3	Fixes to ethernet full duplex operation
B3 --> B4	Corrected error code 0800 (ICD bus parity error)
B4 --> C0 C3	Reprioritized handling of frames based on frame types to prevent timeouts in managed networks
C4 --> C7	Fix to RIPL
C7 --> CB	Changes how AutoSense works (see NOTE below)
CB --> CC	Adds TRFDX (token-ring Full Duplex) support - "BETA"
CC --> CG	Changes to TRFDX, fix a cable sense problem in 'CC',  fixes to RPL on PCI adapters
CG --> D0	Minor changes for FDX Draft 4 compatability

NOTE: To establish compatability with some speed-detecting hubs (ie. 3Com and Synoptics) the AUTOSENSE algorithm has been changed. Microcode prior to 'CB' would allow an adapter set to AUTOSENSE, which had a 'saved speed', to be the first to open on a ring; this is no longer the case. It is still  recommended that any servers have their adapters set to fixed speeds (16 or 4).

  Adapter diagnostic failures, adapter checks, the amber LED on solid, or the adapter being dropped in a managed network are all indications that a microcode upgrade could fix the problem.

Flash Microcode Update Utility 1.60 for Streamer Adapters: filename is STRFLASH.EXE dated 3/28/97.  IBM Auto LANStreamer MC32, Dual EtherStreamer MC 32, EtherStreamer MC 32 Adapter There are important usage notes in the README.TXT on the diskette.

Streamer Log Utility The Utility allows you to view the message log maintained in flash memory on the Auto LANStreamer MC32 Adapter, Dual EtherStreamer MC 32 Adapter, Dual LANStreamer MC32 Adapter and the EtherStreamer MC 32 Adapter STRLOG.EXE

NOTE: For PCI/MCA systems- DOES NOT SUPPORT THE TRIPLE LANSTREAMER PCI ADAPTER. DO NOT USE THIS ROUTINE WITH A TRIPLE LANSTREAMER PCI INSTALLED.

Using STRMRLOG & FLASH exec in a MC/PCI system
   Early versions of STRMRLOG (for gathering fail log data) and FLASHC3 and STRFLASH (for updating  microcode) on the Auto LANStreamer MC32 and Dual LANStreamer MC32 had problems in a PC 750.
   The STRMRLOG exec wouldn't work and stopped the system. The FLASHC3 and STRFLASH exec wouldn't work and would ERASE the microcode on the card, which is unrecoverable by the customer.
   The problem was due to the split bus architecture and timings used in the utilities. This means the problem would be encountered in any PCI/MCA split bus system (PC 730, Server 720, etc.)
STRLOG Version 1.00 (note: not the old STRMRLOG)has been fixed. STRFLASH Version 1.10 and newer have been fixed.  (NOTE: There still remains a problem with using STRFLASH in  PCI/MCA Server 320 and PCI/MCA Server 520 for updating MCA  adapters. PCI adapters are unaffected. There is a warning in the READ.ME on the STRFLASH diskette.)
  This applies to the Auto LANStreamer MC32, Dual EtherStreamer MC 32, Dual LANStreamer MC32 and EtherStreamer MC 32.

MicroChannel Adapters in PCI/MCA Systems
   There is a hardware incompatability issue between the MicroChannel adapters of the Streamer family and the PCI/MCA bridge chips used in PCI/MCA split bus systems from IBM. These systems include Server 310, Server 320, Server 520, Server 720, PC 330, PC 350, PC 730 and PC 750. The incompatability concerns MicroChannel Data Streaming mode.

NOTE: For Server 320, 520 and 720, also see article GI1985, "Tuning Adapters in Server 320/520/720".l

   The adapters affected are: LANStreamer MC32, Auto LANStreamer MC32, Dual LANStreamer MC32, EtherStreamer MC32 and Dual EtherStreamer MC32. The LANStreamer MC16, Auto LANStreamer PCI and Triple LANStreamer PCI adapters are not affected.
   A hardware change was made to the following adapters: Auto LANStreamer MC32, Dual LANStreamer MC32, EtherStreamer MC32 and Dual EtherStreamer MC32. The original LANStreamer MC32, which stopped production in 1994, was not corrected and should not be used in any of these systems. Full details HERE

W95 driver for Lan Adapter /A
    With acknowledgment to Jordi Estrela for discovering that the "IBM PS/2 Adapter/A for Ethernet Networks" (Card Id.s EFD4, EFD5, EFE5) is/are OEM-flavour WD8003E/A cards try selecting the 'canned' "SMC EtherCard PLUS/A (MCA) (WD 8003E/A or 8003ET/A)" driver (generic SMC8000W.VXD NDIS3 driver) 

P.S. if your IBM card does not have one of the above Card Id.s then check other SMC varieties.

LTA0005E Driver Initialized For Wrong Mode
   This can be the result of a simple syntactical problem when using the DOS NDIS driver IBMENI.DOS. When the Adapter for Ethernet TP, Adapter/A for Ethernet  or the LAN Adapter for Ethernet CX is configured for shared RAM mode the parameter RAMADDRESS in PROTOCOL.INI locates the RAM in upper memory. If the adapter is changed to IO mode the presence of this parameter can cause the error message. To solve it simply comment out or remove the RAMADDRESS parameter from  PROTOCOL.INI.

IBM Auto LANStreamer MC32 Adapter

TRMALS1.EXE	Driver Diskette	454,237
TRMALS2.EXE	Option/Diagnostic/NDIS3 Driver	623,640

IBM LANStreamer MC16 Adapter

TRMLS321.EXE	Drivers diskette	507,637
TRMLS16.EXE	Diagnostics/Options  v2.0 (720k)	342,824

   NOTE: The diskette image requires a 720k diskette, not 1.44M.

LT00050 Duplicate Node Addresses Exist
When a LANStreamer MC32 or LANStreamer MC16 is run on a ring at 4 MBps, using the IBMMPC.OS2 or IBMMPC.DOS MAC driver versions 4.01 thru 4.54, with the PROTOCOL.INI parameter LoopBack set to "NO", an LT00050 error will be posted by the LANDD driver and the adapter will not open onto the ring.
   Fix Don't set LoopBack="NO" in PROTOCOL.INI when running on a 4 MBps ring.

Streamer Adapter usage in IBM PC Server 720
IBM Auto LANStreamer MC32, Dual EtherStreamer MC 32, Dual LANStreamer MC32, EtherStreamer MC 32 Adapter

STRS720.EXE	Streamer Package for Server 720	433,334
STRLOG.EXE	Streamer Log Utility	287,338

IBM EtherStreamer MC 32 Adapter

ETMES.EXE

Drivers/Diagnostic/Option  v2.0

477,768

Incompatibility With Certain AUI Concentrators
   Incompatibilities exist between the IBM EtherStreamer MC 32 Adapter andcertain AUI concentrator boxes. Specifically, when the EtherStreamer is attached via its AUI connector to some AUI concentrator boxes, the EtherStreamer will not be able to receive any frames sent from other adapters attached to the same concentrator box. This problem does NOT affect 10Base-T configurations.
   The problem occurs because certain AUI concentrator boxes broadcast the SQE test signal to all of their ports. This SQE test signal is seen by EtherStreamer as a collision indication and is associated with the preceeding frame which, as a result, is discarded.

   The problem can be bypassed by disabling the SQE test function in the AUI concentrator box. This can be done by enabling the external expansion port of the AUI concentrator box. To enable the expansion port, a MAU must be attached to the expansion port of the concentrator box, the network side of the MAU must be properly terminated and the SQE Test function of the MAU must be disabled (usually by a dip switch). In this configuration, EtherStreamer will function with these AUI concentrator boxes. The AUI concentrator boxes which are known to exhibit compatibility problems are:
   Digital Equipment Corporation (DEC) Delni Allied CentreCom 810
The use of these AUI concentrator boxes is likely to be higher in 3172 installations which use EtherStreamer adapters.

IBM Dual EtherStreamer MC32

ETMDES.TXT	Release Notes	10,543
ETMDES.EXE	Drivers/Diagnostic/Option  v2.0	578,454

   The LAN Streamer Adapters and NT 4.0 *require* to have at least SP3 installed before the adapter is properly recognized (false MCA slotnumber ....)
   Install SP3 - then use the path "control panel" - "network" - "adapters" - "add ... " - "IBM Streamer family" to install the card.
   I have the TR MC32 running in my 9585 ... no problems. Best card of all.
   NT 3.51 should work with the TRPALS4.EXE (4th disk) of the PCI Lan Streamer adapter. There is a directory WINNT on this disk as far as I recall. No odd slot misrecognitions under 3.5x.
   M$ had a temporary fix for the 4.0 problem on its page - but it is no longer required after SP3.

LTC0031   invalid address in the adapter 'address' field
This error will occur if the user tries to put an invalid address in the Auto LANStreamer MC32 or Dual LANStreamer MC32 Adapter 'address' field. The address field should be used if a locally administered address is to be added.  If the burned-in address is to be used, leave this field blank. Most common errors are:
  - address too long
  - address too short
  - address not enclosed in double quotes
  - address contains non-hexadecimal digits

LTC0029  No Auto LANStreamer MC32 or Dual EtherStreamer MC 32 Adapter adapter that is supported by this device driver was found ...
The most common reasons are:
1. A down-level driver. Get the latest device-driver diskette
2. For Micro Channel adapters, the system ABIOS is missing or incorrect. Copy the ABIOS.SYS and *.BIO files from the system reference disk to the OS/2 directory.
 

NDIS 3.0 Driver for Windows 95/NT
IBM Auto LANStreamer MC32, Dual LANStreamer MC32, EtherStreamer MC32, Dual EtherStreamer MC32 Adapter

STRNDIS3.EXE

NDIS 3.0 Device Driver Disk

390,162

Slot 8 Incompatability in 8595 and  9595
A 00017100 (171) error occurs on POST (Power-On System Test). This problem may occur on 8595/9595 models xLx or xHx systems during the installation of any of the following adapters in micro channel slot 8:
- IBM LANStreamer MC 32 / 16 
- IBM EtherStreamer MC 32 
- IBM Auto / Dual LANStreamer MC 32
- IBM Dual EtherStreamer MC 32
Fix (Pretty wild, eh?)
Do not install any of the affected adapters in slot 8. Relocate any of the affected adapters to one of the other microchannel slots.

IBM TURBOWAYS 100 ATM MC Adapter As of 04/24/00
ATLESTR.EXE  TW100 MC Driver for Token-Ring LANE Server - ver. 1.23
ATLESET.EXE   TW100 MC Driver for Ethernet LANE Server - ver. 1.23
ATM100OC.EXE  TW100 MC OS/2 LEC Driver - ver. 2.02
ATM100OS.EXE  TW100 MC OS/2 Driver - ver. 1.30
ATM100OI.EXE   TW100 MC OS/2 CIP Driver - ver. 2.02 

PROTMAN.OS2 Failed to Load
After installing the Turboways 100 ATM MC Adapter software in MPTS or LAPS, PROTMAN.OS2 fails to load when booting up.
Check that-
1) All files are copied to either c:\ibmcom or c:\ibmcom\macs. 
2)  CONFIG.SYS has PROTMAN.OS2 statement and the path is correct.
3) No more than one PROTMAN.OS2 file in all directories. 

IBM TURBOWAYS 155 ATM MC MMF Adapter As of 04/24/00
ATM155TC.EXE   TW155 MC Driver for Netware Token-Ring File Server - ver. 1.10
ATM155EC.EXE   TW155 MC Driver for Netware Ethernet File Server - ver. 1.10
ATM155OI.EXE   TW155 MC OS/2 CIP Driver - ver. 2.02
ATM155OC.EXE   TW155 MC OS/2 LEC Driver - ver. 2.02
ATM155OS.EXE   TW155 MC OS/2 Driver - ver. 1.30

Wiring FDDI Directly
From Spooky
   Has anyone worked with FDDI cards from IBM the ones with DB9? I've installed them but don't
know how to use them. A direct link must work but how?

Later, Spooky figures it out-
   Connect 1 to 5 and 6 to 9, first at one card the led was blinking, checked the cable again,
made a wrong connection. Rewired it and it is working.
   Read speed around 4000 KBps, write speed around 2200 KBps (TR around 1200 KBps)
   Server IBM FDDI and Madge TR card, workstation Olicom PCI TR and IBM FDDI.
Novell 4.2 & NT WS 4.0