eravin@dasys1.UUCP (Ed Ravin) (08/27/87)
When we try to set up a UUCP line between IBM "System V" Xenix and either a Microvax-II running Ultrix or an Intel 310 running Intel 286 Xenix the conversation always locks up in the same way: (output of a uucico -x5 connection attempt from Xenix to Intel 310 named "ubik") finds called getto called call: no. ttya5 for sys ubik Speed: want 9600 use 15 ps 6 login called wanted <ogin:> REMOTE returned <<timeout>>--fail sent <<cr>>wanted <ogin:> REMOTE returned <^M^Jlogin:>--ok sent <uucp><cr>>msg-ROK Rmtname ubik, my Role MASTER, Spool - /usr/spool/uucp Ifn - 3, Ofn - 3, Loginuser - elr rmesg - 'P' got Pg wmesg 'U'g alarm 1 alarm 1 alarm 1 alarm 1 And so on, until until the connection is aborted. Placing a Datascope on the line reveals that while the master side is timing out, packets are being sent out on the line but not recognized. We've also had the Intel 310 in master mode report "bad header" over and over again at that stage in the attempted communication. Anybody out there have any idea what's going on here? I can hardly believe that IBM managed to break UUCP under certain condtions. Our AT's running Xenix have no problems talking to anybody else, and the Microvax-II Ultrix is also capable of squawking with other Unix systems. Please email your much-appreciated replies... -- Ed Ravin eravin@dasys1.uucp Programmer-at-Large (a.k.a. cmcl2!cucard!dasys1!eravin) Do androids dream of electric sheep?