Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!genrad!decvax!ucbvax!UOFMCC.BITNET!UOWRAK From: UOWRAK@UOFMCC.BITNET.UUCP Newsgroups: mod.computers.vax Subject: What is TCP-IP? Message-ID: <8704071305.AA06199@ucbvax.Berkeley.EDU> Date: Mon, 6-Apr-87 16:14:00 EST Article-I.D.: ucbvax.8704071305.AA06199 Posted: Mon Apr 6 16:14:00 1987 Date-Received: Fri, 10-Apr-87 03:04:26 EST Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 37 Approved: info-vax@sri-kl.arpa There has been a reasonable amount of information on TCP-IP flying back and forth on INFO-VAX in the past few months. I am starting to suspect that this is a useful software package for me. Maybe someone (some several?) out there have comments for me. 1) What is TCP-IP? Is it useful for linking up VMS systems (two 750's) and UNIX systems (NCR Tower)? What are its capabilities? 2) Is TCP-IP a good way to hook terminal servers to VMS or UNIX systems? Some third-party PACX vendors are talking to me about using their switches instead of DEC's terminal servers. 3) I gather that TCP-IP runs over ethernet co-ax. If I already have my VAXen talking via DECnet/Ethernet using DEUNA's and a DELNI, can this setup co-exist with a TCP-IP function? (I am not sure the last question even makes sense. I keep hearing mutterings that "Ethernet and 802.3 are two different things and can/cannot co-exist on the same co-ax/DELNI". Any comments? Thanx in advance for any replies. If I get a pile of useful stuff, I will pare it down and re-broadcast to the network. Roger Kingsley, Computer Services, The University of Winnipeg, 515 Portage Avenue, Winnipeg, Manitoba Canada R3B 2E9 204/786-9449 UOWRAK@UOFMCC.BITNET