romain@pyrnj.uucp (Romain Kang) (08/12/85)
I'm having trouble trying to call up a Unix PC with uucp, but
I keep getting a bad handshake message I've never seen before.
Has anyone out there ever seen anything like this? What are
the remedies? I'm at a disadvantage here because I don't have
access to the Unix PC.
...
root unixpc (8/12-10:17-12706) SUCCEEDED (call to unixpc )
imsg sync<\020>got it
imsg input<Shere=unixpc\000>got 11
omsg <^PSpyrnj -Q0 -x5>
imsg sync<\020>got it
imsg input<RLOGIN\000>got 6
msg-RLOGIN
root unixpc (8/12-10:17-12706) HANDSHAKE FAIL (LOGIN)
...
"It ain't honey danber. It ain't 4.3. Ain't 4.2. Ain't S5.0. Ain't V7.
Dang!"
--
--Romain Kang, Pyramid Technology Corporation
US Mail: 900 Route 9, Woodbridge, NJ 07095
Ma Bell: (201) 750-2626
UUCPnet: {allegra,cmcl2,princeton,topaz}!pyrnj!romainpeter@baylor.UUCP (Peter da Silva) (08/14/85)
> I'm having trouble trying to call up a Unix PC with uucp, but > I keep getting a bad handshake message I've never seen before. I'm getting the same message from a Callan Data Systems 200 workstation with SV. All names are 6 character (hyd-pt, datafa, etc) and we're talking through a hayes and a Prometheus modem. -- Peter da Silva (the mad Australian) UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter MCI: PDASILVA; CIS: 70216,1076
tim@cithep.UucP (Tim Smith ) (08/21/85)
> > I'm having trouble trying to call up a Unix PC with uucp, but > > I keep getting a bad handshake message I've never seen before. > > I'm getting the same message from a Callan Data Systems 200 > workstation with SV. All names are 6 character (hyd-pt, datafa, etc) > and we're talking through a hayes and a Prometheus modem. Gee, maybe you two should get together and see if the Callan can talk to the Unix PC! :-) But seriously, I have seen this sort of thing before. For example, at Callan, we once were going to get a newsfeed from SDC. However, we could not get our UUCP to talk to their UUCP. However, we have had absolutely no trouble with machines at Bunker Ramo or Dual. We never did find out what was wrong. Maybe someone who has access to a lot of machines should put together a list of what UUCPs can talk to which other UUCPs and post it somewhere. Any volunteers? -- Tim Smith ihnp4!{wlbr!callan,cithep}!tim
guy@sun.uucp (Guy Harris) (08/25/85)
> Maybe someone who has access to a lot of machines should put together a list > of what UUCPs can talk to which other UUCPs and post it somewhere. Any > volunteers? Maybe somebody should post which UUCPs *can't* talk to which other UUCPs, and get the party at fault to fix their UUCP. That same somebody should make sure the problem is that a UUCP is broken, not that the UUCP was set up incorrectly. By and large, most UUCPs will talk to most other UUCPs because most UUCPs are, by now, not broken (or not too badly broken, anyway). Guy Harris
peter@graffiti.UUCP (Peter da Silva) (08/30/85)
> > > I'm having trouble trying to call up a Unix PC with uucp, but > > > I keep getting a bad handshake message I've never seen before. > > > > I'm getting the same message from a Callan Data Systems 200 > > workstation with SV. All names are 6 character (hyd-pt, datafa, etc) > > and we're talking through a hayes and a Prometheus modem. > > Gee, maybe you two should get together and see if the Callan can talk to > the Unix PC! :-) Seriously, we tried this with another UNIX-PC. No go. The PC talked fine to a SV and a V7 uucp. Mysteries. And I hope everyone knows about the checksum problems on the old Unisoft SIII uucps.