Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!uakari.primate.wisc.edu!ginosko!gem.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!TWG.COM!ljm
From: ljm@TWG.COM (Leo J McLaughlin)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: LAN Manager
Message-ID: <8909281520.ac21874@Obelix.TWG.COM>
Date: 28 Sep 89 22:09:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20



>One major problem with LAN Manager is that its only programming
>interfaces are the "Named Pipes" and Netbios NCB interfaces.  There is
>no defined method of getting at an unadulterated transport protocol
>connection; whether the transport is XNS or TCP or OSI the lowest you
>can get is a Netbios session.  So the LAN Manager "standard" can't
>talk to anything except other LAN Managers or Netbioses without vendor
>extensions (which won't be standard unless/until the market produces
>one).

Well, yes and no.  As it happens, Microsoft's LAN Manager for DOS and
LAN Manager for OS/2 use names pipes to speak to NetBIOS over NetBEUI.
However, that part of the LAN Manager API which constitues names pipes
is a perfectly reasonable (well mostly reasonable) transport API.

enjoy,
leo j mclaughlin iii
The Wollongong Group
ljm@twg.com