Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!bionet!ames!pasteur!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: LAN Manager (was PC/NOSs)
Message-ID: <8909272119.AA00481@vax.ftp.com>
Date: 27 Sep 89 21:19:27 GMT
References: <8909272107.AA24933@uhura.cc.rochester.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23


   Date: Wed, 27 Sep 89 17:07:28 -0400
   From: Ted Mead 

   > 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).

   So, what tranport protocol does  LAN Manager use? How  does SMB fit in
   with LAN Manager?

LAN Mnager uses whatever transport protocol the LAN Manager OEM (or the end
user) chooses to add to his PROTOCOLS.INI file, assuming that it presents
a standard Netbios-style NCB interface as appropriate for the operating
system in use.  It doesn't care if it is OSI or TCP or XNS, it uses its'
own constructs (Server Message Blocks, familiar to those of you who've
investigated MS/Net or the PC LAN Program) on top of Netbios "sessions".

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901