home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gumby!destroyer!news.itd.umich.edu!wilson.itn.med.umich.edu!user
- From: Wayne.Wilson@med.umich.edu (Wayne.Wilson)
- Newsgroups: comp.sys.novell
- Subject: Re: Novell vs. Lan Manager, which one do I choose?
- Followup-To: comp.sys.novell
- Date: 17 Nov 1992 14:53:51 GMT
- Organization: Univesity of Michigan Medical Center
- Lines: 23
- Distribution: world
- Message-ID: <Wayne.Wilson-171192095110@wilson.itn.med.umich.edu>
- References: <74315@hydra.gatech.EDU> <1992Nov11.161314.3615@novell.com> <1992Nov12.132051.8471@uk03.bull.co.uk> <74727@hydra.gatech.EDU>
- NNTP-Posting-Host: wilson.itn.med.umich.edu
-
- In article <74727@hydra.gatech.EDU>, bob@comlab.gatech.edu (Bob Baggerman)
- wrote:
-
- > First and foremost, LanMan is protocol independent. LanMan comes with
- > a small, fast non-routable protocol (NetBEUI) and a larger, routable
- > protocol (TCP/IP) as standard equipment. If those protocols don't suite
- > you other vendors protocol stacks can be used instead. XNS, NBP, OSI,
- > DECnet, and other flavors of TCP/IP come to mind.
- >
- MY experience with LanMan on TCP/IP was from the first release of the
- product from HP, but I was very disappointed to find out that you could not
- place clients on the other side of a router port. LanMan was basically
- implemented on top of NETBIOS and the TCP/IP implementation of NETBIOS that
- HP used would not propagate the NETBIOS broadcasts through the router
- ports.
-
- Has this changed since MS took over the TCP/IP support?
-
- Wayne D. Wilson
- Asst. Dir.
- Health Sciences Information & Networking
- University of Michigan Medical Center
- Wayne.Wilson@med.umich.edu
-