Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think.com!mck-csc!
From: claman@csc-sun.mckinsey.com (Larry Claman)
Newsgroups: comp.dcom.lans
Subject: Banyan <-> TCP/IP
Message-ID: <CLAMAN.91Jan17153504@csc-sun.mckinsey.com>
Date: 17 Jan 91 20:36:46 GMT
Sender: @mck-csc.mckinsey.com
Organization: McKinsey & Co., Inc., Cambridge, MA
Lines: 35

Our company is in the planning stages of connecting a SUN network to a Banyan
network via ethernet.  Both systems currently reside on the same ethernet
segment.  We are currently investigating the possibility of using a TCP/IP
connection.  In-house support for TCP/IP is relatively extensive on the SUN side
and minimal on the Banyan portion.  Although this type of connection is
supported at various levels by both vendors, functionality seems to be the major 
issue.  We would like to achieve the following:

	1.	Printer sharing
			- print from Sun to Banyan printers & vice-versa
	2.	File access
			- Can you FTP files in both directions?
			- Can Banyan PCs mount the Sun's file system (via NFS)?
			- Could the Sun have access to the Banyan file system? 
	3. 	Ability for Sun stations to access our IBM mainframe via Banyan's
		SNA communication gateway.
	4.	Dial-in through Banyan modem pool to run sessions on the
		SUN stations.
			- Can you telnet, ftp, etc while dialed in?
			- Can you mount the Sun's file system via NFS while
			  dialed in?	
	5. 	Mail integration
			- Is there a Banyan / SMTP mail gateway?
			- What does the Email gateway do to binary attachments?
	
We would greatly appreciate any insight or suggestions that you can share
regarding inter-connection of these two systems.  In particular, information on
the level of integration to expect, the steps necessary to install this type of
connection, or suggested products to accomplish the above 5 goals.

If there is interest, I will summarize & post the responses.

	Larry Claman
	McKinsey & Co, Cambridge Systems Center
	claman@csc.mckinsey.com