ROUTE.SYS in the OS/2 2.11 Netware Requester

World         Australia | Europe | North America | Singapore
Europe        Austria | Birmingham | Budapest | France | Italy | London | TeamOS/2 (Germany)
North America Berkeley | Chattanooga | Minnesota | Nova Scotia | Ontario | Pennsylvania | TeamOS/2
Last update: 6th November, 1995

Symptoms

TCP/IP not working correctly on Token Ring when using the Netware 2.11 requester and ODI drivers. Able to ping IP addresses on the local ring but not able to ping outside of the ring.

Hardware

Any Token Ring card in a source-routed environment

Problem

The ROUTE.SYS (dated 10-20-94 5:52p with a size of 47488 bytes) in the 2.11 requester has a rather large bug. It will not set the source-routing bit the second frame type--usually token-ring_snap. While you are using ODI drivers, you depend on the Netware code to mark the token-ring_snap frames as source-routable. This means that if you are using IBM's TCP/IP but not the NDIS drivers you are vulnerable. You are also vulnerable if you are using LAN Workplace for OS/2 with either NDIS or ODI adapter drivers. TCP/IP on Token Ring defaults to the token-ring_snap frame type and if the frames are not marked source-routable, the frame won't get past the closest Token Ring bridge.

Procedure

There are a couple of work arounds:

Notes

Novell now has a fix distributed in R211FT.EXE dated on or after 3-24-95.
      ftp://ftp.novell.com/pub/netwire/novfiles/client.kit/os2/fixes/r211ft.exe

To use the above URL wirh WE/2, be sure your explore.ini is set up to transfer .exe files as binary.


Matt Hickman
[ The Warp Pharmacy | News | Hardware | Software | Symptoms | Procedures | References | Commerce | Search | More Help!!! ]