Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!im4u!ut-sally!seismo!mcvax!ukc!dcl-cs!david
From: david@comp.lancs.ac.uk (David T. Coffield)
Newsgroups: net.micro.pc,net.unix-wizards
Subject: MIT TCP/IP query
Message-ID: <339@comp.lancs.ac.uk>
Date: Wed, 6-Aug-86 10:22:22 EDT
Article-I.D.: comp.339
Posted: Wed Aug  6 10:22:22 1986
Date-Received: Sat, 9-Aug-86 05:32:21 EDT
Reply-To: david@comp.lancs.ac.uk (David T. Coffield)
Organization: Department of Computing at Lancaster University, UK.
Lines: 20
Xref: watmath net.micro.pc:9515 net.unix-wizards:19090

We have the MIT TCP/IP package for the IBM PC and are about (maybe) to buy
a 3Com Etherlink board to allow us to snap one onto our Departmental
Ethernet - which consists of a VAX and several Suns, running 4.2 BSD TCP/IP.

Part of the MIT information states that the BSD TCP/IP is non-standard
in several ways. Has anyone any experience of using the MIT package in
a BSD environment? What does "investing some effort in adjusting your
4.2 configuration" mean?? The intention was to be able to do remote
logins and file transfer to/from the PC from/to the VAX and Suns. Can we
do this, or are there a lot of problems on the BSD side?

Any pointers, hints, tips etc appreciated.
Reply by email, and I'll summarise if necessary.

	Thanks,
		David.
-- 
uucp:   ...!mcvax!ukc!dcl-cs!david     post: Department of Computing
arpa:   david%lancs.comp@ucl.cs              University of Lancaster, UK
janet:  david@uk.ac.lancs.comp	       phone: +44 524 65201 x 4599