PAP4@AI.AI.MIT.EDU ("Philip A. Prindeville") (10/23/87)
(PCIP readers: I call your attention to the last paragraph. If you respond, reply to both lists.) > The PC's should also be able to run a PC-network over the same cabling for > exchanging messages and retrieving files from a PC fileserver. There isn't any real difficulty in running multiple protocols over the same ethernet (except Novell Netware and Xerox XNS). But, why make your mail facilities dependent on the PC? Use of an open protocol, machine independent mail system like SMTP would provide greater interoperability should you require it in the future. > Access to Email-facilities would be through our EARN/BITNET-connected 9370. There are also numerous software packages to convert SMTP/TCP to BITNET mail. That you are reading this message proves that... > 1. Does anybody have experience with the IBM (host and PC) TCP/IP product in > connection with the Ethernet board on the 9370 ? Sorry, no. Too new for me. > 2. Does anybody have experience with TCP/IP products for PC's vs. IBM hosts ? I've seen the UMD/IBM code and the UCLA code run fairly well with PCs and other micros. No experience with WISCNet or Fibronics KNET... > 3. Can a PC run both TCP/IP to the host and some other networking program > communication to the other PC's ? Yes -- if it is well behaved (see previous message). Again I'll warn against getting locked into proprietary or manufacturer-specific protocols... > 4. How do we hook the remote LAN into the host, directly into the Ethernet > board or via a bridge onto the local Ethernet LAN ? By host I assume you mean the 9370. If you did `hook it directly' to the 9370, it would be via a serial interface, since you are using 9.6kbs lines to link the networks... Another approach would be to use a gateway, possibly a dedicated machine. Does anyone have any have any experience linking ethernet islands via Phil Karn's package? Ease of configuration, reliability, and throughput info would be of great interest. -Philip