Re: NT was written before the Internet says security expert

From: Jeff Liebermann (jeffl_at_comix.santa-cruz.ca.us)
Date: 03/10/04


Date: Wed, 10 Mar 2004 00:16:11 GMT

On Tue, 9 Mar 2004 21:08:59 +0000 (UTC), Ian Wilson
<scobloke2@infotop.co.uk> wrote:

>Jeff Liebermann wrote:
>> The real innovation by Microsoft was implimenting *MULTIPLE* transport
>> protocols in Windoze 3.1 through NDIS and ODI network interfaces.
>> Within reasonable limitations, you could run NETBIOS over multiple
>> transport protocols. This was new as other network products tended to
>> support only one transport protocol at a time.
>
>I have in front of me "PC/TCP Interoperability" by FTP Software Inc
>dated 1991. I think I threw away some older versions of this publication
>($10.00).

Argh. My copy went in the dumpster (along with Sun PC-NFS and such)
about a month ago. It never fails. I need it immediately after I
toss it.

>CHAPTER 3 SECTION 3-4 Running Multiple Protocol Stacks over a Packet Driver.
>
>FTP's PC/TCP supported NDIS, ASI, ODI, DLL and Packet-Driver
>architectures. It supported Banyan VINES, Netware, LAN-Manager,
>Pathworks and NFS.
>
>Maybe I'm wrong but I recall this was before MS even had a TCP/IP stack.
>
>http://www.crynwr.com/packet_driver.html
>"Copyright (c) 1986, 1989 by FTP Software Inc ...
>Protocol implementations that use the packet driver can completely
>coexist on a PC and can make use of one another's services, whereas
>multiple applications which do not use the driver do not coexist on one
>machine properly. Through use of the packet driver, a user could run
>TCP/IP, XNS, and a proprietary protocol implementation such as DECnet,
>Banyan's, LifeNet's, Novell's or 3Com's without the difficulties
>associated with pre-empting the network interface."

I stand corrected. As I vaguely recall, one could initially use
either the packet driver interface, NDIS (from Microsoft), or ODI
(from Novell) with DOS applications. Some supplied their own drivers
or would only support one of the 3 flavours (i.e. NCSA telnet). Only
Microsoft supported simultaneously using NDIS and ODI, but not with
the packet driver driver. Each of these network link level interfaces
would act as a demultiplexer for the various protocols and could
theoretically handle almost any protocol that supported the interface.
That's where I remember running into trouble. 3rd party or even OEM
NDIS and ODI drivers would frequently fail to coexist with others.
Microsoft took care of the integration and supplied many of these
drivers in the Windoze 3.11 package. FTP Software and others did not
and relied on the ethernet card vendors to supply NDIS and ODI
interfaces. If you look carefully at the Windoze driver disks
supplied with todays ethernet cards, NDIS drivers are always included,
while ODI and packet driver drivers are sorta optional. Anyway, at
the time, I had zero luck getting a multi-vendor conglomeration of
drivers and protocol stacks to play.

-- 
# Jeff Liebermann   150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice    http://www.LearnByDestroying.com
#                           jeffl@comix.santa-cruz.ca.us
# 831.421.6491 digital_pager  jeffl@cruzio.com     AE6KS


Relevant Pages

  • Re: different NDIS Handler in IM?
    ... > edge is the miniport interfacing Protocol driver. ... An NDIS IM driver is a "hybrid" combination of two different NDIS driver ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS Irda protocol driver
    ... I am developing NDIS IrDA protocol driver and facing a problem in receiving ... IrDA packet from NDIS. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc.
    ... do possible to read/write on handle opened with CreateFile on NIC. ... microsoft.public.development.device.drivers and we'll wait for NDIS gurus ... > Usually you can't do this because not driver but NDIS created security ... > Miniport in NDIS have no knowledge about protocol above it, ...
    (microsoft.public.win32.programmer.networks)
  • Re: Incorrect server name
    ... There is no primary WINS server defined for this adapter. ... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) ... Network Monitor Driver ...
    (microsoft.public.windows.server.general)
  • Re: Question about FILE_OBJECT
    ... NDIS IM is a driver that fully conforms to the model, ... I.E. every time they allocated a new context object they ...
    (microsoft.public.win32.programmer.kernel)