Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!sdd.hp.com!samsung!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!wam!mikec
From: mikec@wam.umd.edu (Michael D. Callaghan)
Newsgroups: comp.sys.next
Subject: Re: Next <--> AT serial connect?
Message-ID: <1991Jan7.040057.27718@wam.umd.edu>
Date: 7 Jan 91 04:00:57 GMT
References: <5058@idunno.Princeton.EDU>
Sender: usenet@wam.umd.edu (USENET Posting)
Reply-To: mikec@wam.umd.edu (Michael D. Callaghan)
Organization: University of Maryland at College Park
Lines: 34

In article <5058@idunno.Princeton.EDU> amlovell@phoenix.Princeton.EDU (Anthony M Lovell) writes:
>I just got a NeXT cube, (with 040 upgraed on order).  I have it at home
>next to a 386 DOS machine.  What methods (hardware & software) exist
>that would allow me to connect these devices (ala LapLink) and exchange
>data, even if I enjoy only trivial facilities?

For what it's worth, I have a NeXTcube 030, sitting next to a 286
AT compatible. With the help of a High School friend, a 3Com 503
ethernet card, and a PC/IP setup, (less than $300 including cabling),
I'm now set up on the NeXT network. It took all day today to get it
running, but I can now Telnet, ftp, and lpr over to the NeXT.

Translation: My NeXTcube now has a floppy drive!
             My AT now has a laser printer!
             My AT now has an optical drive!

NFS is coming along, but there seems to be a catch. The AT software
doesn't do its own domain name resolution. It looks to the Cube as
a name server. However, I cannot seem to get the NeXT to understand
that it's supposed to be name server.

Anyone?

MikeC

BTW, before the network connection worked, I just used a Mac printer
cable and plugged the other end into a free IBM serial port, and ran
Kermit on both machines.


--
___________________________________________________
Michael D. Callaghan,MDC Designs, University of Merryland
mikec@wam.umd.edu